From: Mark Brown <broonie@kernel.org>
To: zhong jiang <zhongjiang@huawei.com>
Cc: bardliao@realtek.com, oder_chiou@realtek.com,
lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: rt5677: Make rt5677_spi_pcm_page static
Date: Tue, 29 Oct 2019 12:24:35 +0000 [thread overview]
Message-ID: <20191029122435.GD5253@sirena.co.uk> (raw)
In-Reply-To: <5DB7AD30.60007@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
On Tue, Oct 29, 2019 at 11:08:32AM +0800, zhong jiang wrote:
> ping.
> On 2019/10/24 20:15, zhong jiang 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
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-10-29 12:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 12:15 [PATCH] ASoC: rt5677: Make rt5677_spi_pcm_page static zhong jiang
2019-10-29 3:08 ` zhong jiang
2019-10-29 12:24 ` Mark Brown [this message]
[not found] ` <5DB8383C.7040601@huawei.com>
2019-10-29 13:09 ` Mark Brown
2019-10-31 13:20 ` Mark Brown
2019-10-31 13:40 ` zhong jiang
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=20191029122435.GD5253@sirena.co.uk \
--to=broonie@kernel.org \
--cc=bardliao@realtek.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=zhongjiang@huawei.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