[GIT PULL] RISC-V Devicetrees fix for Sophgo/SG2042 v6.8-rc1
Arnd Bergmann
arnd at arndb.de
Thu Jan 25 22:11:06 PST 2024
On Wed, Jan 24, 2024, at 08:50, Chen Wang wrote:
> Hey Arnd,
>
> Please pull one DT fix for Sophgo SG2042 based off v6.8-rc1.
Thank you for the pull request I found a few small mistakes,
so please respin the tag and the email:
>
> are available in the Git repository at:
>
> git at github.com:sophgo/linux.git
> tags/riscv-dt-fixes-sophgo-sg2042-for-v6.8-rc1
This is not a URL I can pull from.
You may want to add something like this in your .gitconfig in
order to turn it into a normal https:// URL when sending
a pull request:
[url "https://github.com"]
insteadOf = git at github.com
> ----------------------------------------------------------------
> RISC-V Devicetrees fix for Sophgo/SG2042 v6.8-rc1
>
> This patch is [2/2] of [1]. The binding part [2] has been merged in
> v6.8-rc1, but
> the dt patch [3] is missed. This fix add the dt patch.
>
> Signed-off-by: Chen Wang <unicorn_wang at outlook.com>
>
> Link:
> https://lore.kernel.org/all/IA1PR20MB4953C912FC58C0D248976564BB86A@IA1PR20MB4953.namprd20.prod.outlook.com/
> [1]
> Link:
> https://lore.kernel.org/all/09b2fc2f-dde9-4f43-9704-d8053bfc85cf@linaro.org/
> [2]
> Link:
> https://lore.kernel.org/all/IA1PR20MB4953669C097D9C9E24B549FFBB86A@IA1PR20MB4953.namprd20.prod.outlook.com/
> [3]
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
More information about the linux-riscv
mailing list