All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Wang <unicorn_wang@outlook.com>
To: soc@kernel.org
Cc: Conor Dooley <conor@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	linux-riscv@lists.infradead.org,
	Inochi Amaoto <inochiama@outlook.com>,
	Xiaoguang Xing <xiaoguang.xing@sophgo.com>,
	haijiao.liu@sophgo.com, Chao Wei <chao.wei@sophgo.com>,
	unicorn_wang@outlook.com
Subject: [GIT PULL] RISC-V Devicetrees fix for Sophgo/SG2042 v6.8-rc1
Date: Wed, 24 Jan 2024 15:50:44 +0800	[thread overview]
Message-ID: <MA0P287MB28228572C526C5099A8BDA2DFE7B2@MA0P287MB2822.INDP287.PROD.OUTLOOK.COM> (raw)

Hey Arnd,

Please pull one DT fix for Sophgo SG2042 based off v6.8-rc1.

Thanks,
Chen.

The following changes since commit 
6613476e225e090cc9aad49be7fa504e290dd33d:

   Linux 6.8-rc1 (2024-01-21 14:11:32 -0800)

are available in the Git repository at:

git@github.com:sophgo/linux.git 
tags/riscv-dt-fixes-sophgo-sg2042-for-v6.8-rc1

for you to fetch changes up to eb37a1537da8c92eadc6bde026c18988b00892c1:

   riscv: dts: sophgo: separate sg2042 mtime and mtimecmp to fit aclint 
format (2024-01-24 14:20:51 +0800)

----------------------------------------------------------------
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@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]

----------------------------------------------------------------
Inochi Amaoto (1):
       riscv: dts: sophgo: separate sg2042 mtime and mtimecmp to fit 
aclint format

  arch/riscv/boot/dts/sophgo/sg2042.dtsi | 80 
++++++++++++++++++++++++++++++++++++++++++++++++--------------------------------
  1 file changed, 48 insertions(+), 32 deletions(-)


WARNING: multiple messages have this Message-ID (diff)
From: Chen Wang <unicorn_wang@outlook.com>
To: soc@kernel.org
Cc: Conor Dooley <conor@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	linux-riscv@lists.infradead.org,
	Inochi Amaoto <inochiama@outlook.com>,
	Xiaoguang Xing <xiaoguang.xing@sophgo.com>,
	haijiao.liu@sophgo.com, Chao Wei <chao.wei@sophgo.com>,
	unicorn_wang@outlook.com
Subject: [GIT PULL] RISC-V Devicetrees fix for Sophgo/SG2042 v6.8-rc1
Date: Wed, 24 Jan 2024 15:50:44 +0800	[thread overview]
Message-ID: <MA0P287MB28228572C526C5099A8BDA2DFE7B2@MA0P287MB2822.INDP287.PROD.OUTLOOK.COM> (raw)

Hey Arnd,

Please pull one DT fix for Sophgo SG2042 based off v6.8-rc1.

Thanks,
Chen.

The following changes since commit 
6613476e225e090cc9aad49be7fa504e290dd33d:

   Linux 6.8-rc1 (2024-01-21 14:11:32 -0800)

are available in the Git repository at:

git@github.com:sophgo/linux.git 
tags/riscv-dt-fixes-sophgo-sg2042-for-v6.8-rc1

for you to fetch changes up to eb37a1537da8c92eadc6bde026c18988b00892c1:

   riscv: dts: sophgo: separate sg2042 mtime and mtimecmp to fit aclint 
format (2024-01-24 14:20:51 +0800)

----------------------------------------------------------------
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@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]

----------------------------------------------------------------
Inochi Amaoto (1):
       riscv: dts: sophgo: separate sg2042 mtime and mtimecmp to fit 
aclint format

  arch/riscv/boot/dts/sophgo/sg2042.dtsi | 80 
++++++++++++++++++++++++++++++++++++++++++++++++--------------------------------
  1 file changed, 48 insertions(+), 32 deletions(-)


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

             reply	other threads:[~2024-01-24  7:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24  7:50 Chen Wang [this message]
2024-01-24  7:50 ` [GIT PULL] RISC-V Devicetrees fix for Sophgo/SG2042 v6.8-rc1 Chen Wang
2024-01-26  6:11 ` Arnd Bergmann
2024-01-26  6:11   ` Arnd Bergmann
2024-01-26  7:06   ` Chen Wang
2024-01-26  7:06     ` Chen Wang
2024-01-26  7:10     ` Arnd Bergmann
2024-01-26  7:10       ` Arnd Bergmann
2024-01-26  7:15       ` Chen Wang
2024-01-26  7:15         ` Chen Wang
2024-01-26 12:31       ` Chen Wang
2024-01-26 12:31         ` Chen Wang
2024-01-26 12:59         ` Arnd Bergmann
2024-01-26 12:59           ` Arnd Bergmann
2024-01-26 13:27           ` Chen Wang
2024-01-26 13:27             ` Chen Wang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=MA0P287MB28228572C526C5099A8BDA2DFE7B2@MA0P287MB2822.INDP287.PROD.OUTLOOK.COM \
    --to=unicorn_wang@outlook.com \
    --cc=chao.wei@sophgo.com \
    --cc=conor@kernel.org \
    --cc=haijiao.liu@sophgo.com \
    --cc=inochiama@outlook.com \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=soc@kernel.org \
    --cc=xiaoguang.xing@sophgo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.