[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191216145625.GF4161@sirena.org.uk>
Date: Mon, 16 Dec 2019 14:56:25 +0000
From: Mark Brown <broonie@...nel.org>
To: John Garry <john.garry@...wei.com>
Cc: marek.vasut@...il.com, tudor.ambarus@...rochip.com,
linuxarm@...wei.com, linux-kernel@...r.kernel.org,
linux-mtd@...ts.infradead.org, linux-spi@...r.kernel.org,
xuejiancheng@...ilicon.com, fengsheng5@...wei.com,
chenxiang66@...ilicon.com
Subject: Re: [PATCH v2 0/3] HiSilicon v3xx SFC driver
On Mon, Dec 16, 2019 at 02:52:23PM +0000, John Garry wrote:
> On 09/12/2019 14:08, John Garry wrote:
> > This patchset introduces support for the HiSilicon SFC V3XX driver.
> >
>
> Hi guys,
>
> Just a friendly reminder on this series.
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.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists