From: patchwork-bot+linux-riscv@kernel.org
To: Chen Wang <unicorn_wang@outlook.com>
Cc: linux-riscv@lists.infradead.org, sboyd@kernel.org,
linux-clk@vger.kernel.org, conor@kernel.org,
inochiama@outlook.com, xiaoguang.xing@sophgo.com,
haijiao.liu@sophgo.com, chao.wei@sophgo.com
Subject: Re: [GIT PULL] RISC-V Sophgo SG2042 clock drivers for v6.11
Date: Tue, 23 Jul 2024 12:58:36 +0000 [thread overview]
Message-ID: <172173951661.10883.11626056916219005908.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <MA0P287MB28221A333D852974F55E3228FEC22@MA0P287MB2822.INDP287.PROD.OUTLOOK.COM>
Hello:
This pull request was applied to riscv/linux.git (for-next)
by Stephen Boyd <sboyd@kernel.org>:
On Fri, 14 Jun 2024 15:28:22 +0800 you wrote:
> Hey, Stephen,
>
> Please pull clock changes for RISC-V/Sophgo/SG2042.
>
> For dts part, I will handle it at my side.
>
> I send this PR just want to expedite patches for this clock driver. The
> patches have gone through 16 rounds of review [1], and I have carefully
> checked and revised all of them based on everyone's comments.
>
> [...]
Here is the summary with links:
- [GIT,PULL] RISC-V Sophgo SG2042 clock drivers for v6.11
https://git.kernel.org/riscv/c/54cb3bb48337
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2024-07-23 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 7:28 [GIT PULL] RISC-V Sophgo SG2042 clock drivers for v6.11 Chen Wang
2024-06-27 10:26 ` Chen Wang
2024-07-05 12:38 ` Chen Wang
2024-07-08 18:56 ` Stephen Boyd
2024-07-23 12:58 ` patchwork-bot+linux-riscv [this message]
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=172173951661.10883.11626056916219005908.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=chao.wei@sophgo.com \
--cc=conor@kernel.org \
--cc=haijiao.liu@sophgo.com \
--cc=inochiama@outlook.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=sboyd@kernel.org \
--cc=unicorn_wang@outlook.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox