From: Mark Brown <broonie@kernel.org>
To: John Keeping <john@metanate.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Jie Yang <yang.jie@linux.intel.com>,
Bard Liao <bardliao@realtek.com>,
Oder Chiou <oder_chiou@realtek.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Ben Zhang <benzh@chromium.org>, Dylan Reid <dgreid@chromium.org>,
Genki Marshall <genki@genki.is>, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH v2 0/2] ASoC: Chromebook Pixel 2015 audio support
Date: Wed, 14 Sep 2016 14:11:51 +0100 [thread overview]
Message-ID: <20160914131151.GW27946@sirena.org.uk> (raw)
In-Reply-To: <20160905153426.72c1caeb.john@metanate.com>
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
On Mon, Sep 05, 2016 at 03:34:26PM +0100, John Keeping wrote:
> On Wed, 24 Aug 2016 22:06:34 +0100, John Keeping wrote:
> Ping? Is there anything I can do to help move this forward?
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, 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: 473 bytes --]
prev parent reply other threads:[~2016-09-14 13:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-14 11:18 [PATCH 0/2] ASoC: Chromebook Pixel 2015 support John Keeping
2016-08-14 11:18 ` [PATCH 1/2] ASoC: rt5677: Add ACPI support John Keeping
2016-08-16 17:20 ` Mark Brown
2016-08-17 10:05 ` John Keeping
2016-08-14 11:18 ` [PATCH 2/2] ASoC: Intel: boards: Add bdw-rt5677 machine driver John Keeping
2016-08-17 16:20 ` John Keeping
2016-08-24 21:06 ` [PATCH v2 0/2] ASoC: Chromebook Pixel 2015 audio support John Keeping
2016-08-24 21:06 ` [PATCH v2 1/2] ASoC: rt5677: Add ACPI support John Keeping
2016-08-29 12:24 ` Tom Rini
2016-09-25 5:57 ` Applied "ASoC: rt5677: Add ACPI support" to the asoc tree Mark Brown
2016-08-24 21:06 ` [PATCH v2 2/2] ASoC: Intel: boards: Add bdw-rt5677 machine driver John Keeping
2016-08-29 12:25 ` Tom Rini
2016-09-25 5:57 ` Applied "ASoC: Intel: boards: Add bdw-rt5677 machine driver" to the asoc tree Mark Brown
2016-09-05 14:34 ` [PATCH v2 0/2] ASoC: Chromebook Pixel 2015 audio support John Keeping
2016-09-14 13:11 ` 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=20160914131151.GW27946@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=benzh@chromium.org \
--cc=dgreid@chromium.org \
--cc=genki@genki.is \
--cc=john@metanate.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=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox