From: Mark Brown <broonie@kernel.org>
To: "Tc, Jenny" <jenny.tc@intel.com>
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"N, Harshapriya" <harshapriya.n@intel.com>,
Jie Yang <yang.jie@linux.intel.com>,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
"Chiang, Mac" <mac.chiang@intel.com>,
"Nujella, Sathyanarayana" <sathyanarayana.nujella@intel.com>,
"M R, Sathya Prakash" <sathya.prakash.m.r@intel.com>,
"M, Naveen" <naveen.m@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH] ASoC: Intel: Boards: Add Maxim98373 support
Date: Thu, 7 Mar 2019 09:56:16 +0000 [thread overview]
Message-ID: <20190307095616.GB6529@sirena.org.uk> (raw)
In-Reply-To: <20ADAB092842284E95860F279283C5645699B4D7@BGSMSX104.gar.corp.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 882 bytes --]
On Thu, Mar 07, 2019 at 01:08:32AM +0000, Tc, Jenny wrote:
> Maintainers,
>
> A gentle reminder for the review.
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 #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2019-03-07 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 16:47 [PATCH v2] ASoC: Intel: Boards: Add Maxim98373 support Jenny TC
2019-02-25 16:47 ` [PATCH] " Jenny TC
2019-03-05 11:06 ` Chiang, Mac
2019-03-07 1:08 ` Tc, Jenny
2019-03-07 9:56 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-19 4:24 [PATCH v2] " Jenny TC
2019-02-19 4:24 ` [PATCH] " Jenny TC
2019-02-25 16:08 ` Tc, Jenny
2019-02-25 16:40 ` 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=20190307095616.GB6529@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=harshapriya.n@intel.com \
--cc=jenny.tc@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=mac.chiang@intel.com \
--cc=naveen.m@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=sathya.prakash.m.r@intel.com \
--cc=sathyanarayana.nujella@intel.com \
--cc=tiwai@suse.com \
--cc=yang.jie@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.