From: Randy Dunlap <rdunlap@infradead.org>
To: Mark Brown <broonie@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Codrin Ciubotariu" <codrin.ciubotariu@microchip.com>,
alsa-devel@alsa-project.org,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Bo Shen" <voice.shen@atmel.com>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
"Alexandre Belloni" <alexandre.belloni@free-electrons.com>
Subject: Re: [PATCH] ASoC: atmel: ATMEL drivers depend on HAS_DMA
Date: Mon, 28 Jun 2021 09:03:25 -0700 [thread overview]
Message-ID: <6734cd67-ae14-74f4-a78e-b6a810c1cdec@infradead.org> (raw)
In-Reply-To: <20210628130214.GB4492@sirena.org.uk>
On 6/28/21 6:02 AM, Mark Brown wrote:
> On Sun, Jun 27, 2021 at 03:28:59PM -0700, Randy Dunlap wrote:
>> [adding LKML]
>>
>> 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.
a. The entire email/patch was there. Should I put the ping _after_ the patch?
Would that help?
b. What do you consider a reasonable time? The patch was sent 28 days
prior to this gentle ping.
> 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.
>
Yes, I shall resend the patch. Thanks.
--
~Randy
next prev parent reply other threads:[~2021-06-28 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210530204851.3372-1-rdunlap@infradead.org>
2021-06-27 22:28 ` [PATCH] ASoC: atmel: ATMEL drivers depend on HAS_DMA Randy Dunlap
2021-06-28 13:02 ` Mark Brown
2021-06-28 16:03 ` Randy Dunlap [this message]
2021-06-28 16:35 ` Mark Brown
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=6734cd67-ae14-74f4-a78e-b6a810c1cdec@infradead.org \
--to=rdunlap@infradead.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=codrin.ciubotariu@microchip.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=voice.shen@atmel.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;
as well as URLs for NNTP newsgroup(s).