From: Mark Brown <broonie@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: alsa-devel@alsa-project.org,
"Liam Girdwood" <lgirdwood@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
"Alexandre Belloni" <alexandre.belloni@free-electrons.com>,
"Bo Shen" <voice.shen@atmel.com>,
"Codrin Ciubotariu" <codrin.ciubotariu@microchip.com>
Subject: Re: [PATCH] ASoC: atmel: ATMEL drivers depend on HAS_DMA
Date: Mon, 28 Jun 2021 17:35:53 +0100 [thread overview]
Message-ID: <20210628163553.GD4492@sirena.org.uk> (raw)
In-Reply-To: <6734cd67-ae14-74f4-a78e-b6a810c1cdec@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 776 bytes --]
On Mon, Jun 28, 2021 at 09:03:25AM -0700, Randy Dunlap wrote:
> On 6/28/21 6:02 AM, Mark Brown wrote:
> > 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
> a. The entire email/patch was there. Should I put the ping _after_ the patch?
> Would that help?
Never send content free pings of any kind. There's an "and" there.
Quoted patches can't be applied.
> b. What do you consider a reasonable time? The patch was sent 28 days
> prior to this gentle ping.
As the mail you are replying to suggests this depends on the patch, some
things are more urgent than others, and in any case like I say content
free pings no matter how content free are just nose.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-06-28 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-30 20:48 [PATCH] ASoC: atmel: ATMEL drivers depend on HAS_DMA Randy Dunlap
2021-06-27 22:28 ` Randy Dunlap
2021-06-28 13:02 ` Mark Brown
2021-06-28 16:03 ` Randy Dunlap
2021-06-28 16:35 ` Mark Brown [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=20210628163553.GD4492@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=alsa-devel@alsa-project.org \
--cc=codrin.ciubotariu@microchip.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=rdunlap@infradead.org \
--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).