[GIT PULL] RISC-V Devicetrees fix for Sophgo/SG2042 v6.8-rc1

[Chen Wang]

On 2024/1/26 14:11, Arnd Bergmann wrote:
[......]
> The tag description is what gets turned into the merge commit
> when I pull it, so it needs to be something that makes sense
> for the long-term git history as well as for me to understand
> why I need to pull it.
>
> For a normal branch, that would mainly mean that you should
> give a summary of the branch contents. In this case, I see you
> have only one patch, so it's probably easier to send that
> patch to soc at kernel.org individually, with the same cc list.
>
>         Arnd

I have one question about your mentiond "send that patch to 
soc at kernel.org individiually ...".  If I sent it as a patch, where 
should I add the explanation of what I explained in this GIT PULL about 
the omission. After all, the content of this explanation is not part of 
the commit of that patch.

Should I send this patch email and then reply it, and then explain in 
the reply email?

Thanks,

Chen