From: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
To: linux-rockchip@lists.infradead.org, linux-sound@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Pei Xiao <xiaopei01@kylinos.cn>
Cc: Pei Xiao <xiaopei01@kylinos.cn>
Subject: Re: [PATCH 0/2] Cleanup in rockchip_sai.c
Date: Wed, 04 Jun 2025 19:48:27 +0200 [thread overview]
Message-ID: <3339020.AJdgDx1Vlc@workhorse> (raw)
In-Reply-To: <cover.1749006565.git.xiaopei01@kylinos.cn>
On Wednesday, 4 June 2025 05:13:28 Central European Summer Time Pei Xiao wrote:
> 1.Simplify the condition logic in
> 2.Use helper function devm_clk_get_enabled()
>
> Pei Xiao (2):
> ASOC: rochchip: Simplify the condition logic in rockchip_sai_xfer_stop
> ASOC: rockchip: Use helper function devm_clk_get_enabled()
>
> sound/soc/rockchip/rockchip_sai.c | 11 +----------
> 1 file changed, 1 insertion(+), 10 deletions(-)
>
>
Hi,
for the v2 of this series, please To/Cc the maintainer that will actually
be merging the patches, not just me. You can get a full list of people to
include as addresses for your series with the ./scripts/get_maintainer.pl
script.
Ideally, you'll use a tool like b4[1] to make your life easier here and
do this for you. That way, Mark Brown won't yell at you as much, and the
responsible people have a higher chance of seeing the patches. The b4
tool has the `b4 prep --auto-to-cc` option for this, and it'll warn you
before `b4 send` if you haven't --auto-to-cc'd before sending. If you
are using your own SMTP server to send and not a b4 relay, you'll
probably want to `b4 send --no-sign`, but a dry run with
`b4 send -o some-dir/` is advisible beforehand so you can look over the
e-mails being generated.
Link: https://b4.docs.kernel.org/en/latest/contributor/overview.html [1]
Kind regards,
Nicolas Frattaroli
prev parent reply other threads:[~2025-06-04 17:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 3:13 [PATCH 0/2] Cleanup in rockchip_sai.c Pei Xiao
2025-06-04 3:13 ` [PATCH 1/2] ASOC: rochchip: Simplify the condition logic in rockchip_sai_xfer_stop Pei Xiao
2025-06-04 17:23 ` Nicolas Frattaroli
2025-06-05 1:57 ` Pei Xiao
2025-06-05 14:30 ` Nicolas Frattaroli
2025-06-04 3:13 ` [PATCH 2/2] ASOC: rockchip: Use helper function devm_clk_get_enabled() Pei Xiao
2025-06-04 17:42 ` Nicolas Frattaroli
2025-06-05 2:00 ` Pei Xiao
2025-06-06 3:27 ` Pei Xiao
2025-06-06 8:26 ` Nicolas Frattaroli
2025-06-04 17:48 ` Nicolas Frattaroli [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=3339020.AJdgDx1Vlc@workhorse \
--to=nicolas.frattaroli@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=xiaopei01@kylinos.cn \
/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