[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160914131151.GW27946@sirena.org.uk>
Date: Wed, 14 Sep 2016 14:11:51 +0100
From: Mark Brown <broonie@...nel.org>
To: John Keeping <john@...anate.com>
Cc: alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
Jie Yang <yang.jie@...ux.intel.com>,
Bard Liao <bardliao@...ltek.com>,
Oder Chiou <oder_chiou@...ltek.com>,
Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>, Ben Zhang <benzh@...omium.org>,
Dylan Reid <dgreid@...omium.org>,
Genki Marshall <genki@...ki.is>, Tom Rini <trini@...sulko.com>
Subject: Re: [PATCH v2 0/2] ASoC: Chromebook Pixel 2015 audio support
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.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists