From: Guixin Liu <kanie@linux.alibaba.com>
To: Mark Brown <broonie@kernel.org>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Sowjanya Komatineni <skomatineni@nvidia.com>,
Laxman Dewangan <ldewangan@nvidia.com>,
linux-tegra@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH] spi: tegra210-quad: downgrade the log when fall back to PIO
Date: Fri, 5 Dec 2025 10:14:49 +0800 [thread overview]
Message-ID: <66457798-e67c-41a1-b1bb-fc8c253c8b30@linux.alibaba.com> (raw)
In-Reply-To: <cb9c67fa-c95e-44a3-b906-8f64bc4a9e29@sirena.org.uk>
在 2025/12/4 20:33, Mark Brown 写道:
> On Thu, Dec 04, 2025 at 09:46:26AM +0800, Guixin Liu wrote:
>> Friendly ping...
> Please don't send content free pings and please allow a reasonable time
> for review. People get busy, go on holiday, attend conferences and so
> on so unless there is some reason for urgency (like critical bug fixes)
> please allow at least a couple of weeks for review. If there have been
> review comments then people may be waiting for those to be addressed.
>
> Sending content free pings adds to the mail volume (if they are seen at
> all) which is often the problem and since they can't be reviewed
> directly if something has gone wrong you'll have to resend the patches
> anyway, so sending again is generally a better approach though there are
> some other maintainers who like them - if in doubt look at how patches
> for the subsystem are normally handled.
My bad, sorry for the trouble, and thanks for the advise.
Best Regards,
Guixin Liu
next prev parent reply other threads:[~2025-12-05 2:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 13:02 [PATCH] spi: tegra210-quad: downgrade the log when fall back to PIO Guixin Liu
2025-12-04 1:46 ` Guixin Liu
2025-12-04 12:33 ` Mark Brown
2025-12-05 2:14 ` Guixin Liu [this message]
2025-12-10 4:24 ` Jon Hunter
2025-12-11 3:44 ` Guixin Liu
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=66457798-e67c-41a1-b1bb-fc8c253c8b30@linux.alibaba.com \
--to=kanie@linux.alibaba.com \
--cc=broonie@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-spi@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=skomatineni@nvidia.com \
--cc=thierry.reding@gmail.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