[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171128151537.jxf4ojjf7n7mnk7r@sirena.org.uk>
Date: Tue, 28 Nov 2017 15:15:37 +0000
From: Mark Brown <broonie@...nel.org>
To: Jonathan Neuschäfer <j.neuschaefer@....net>
Cc: linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
Liam Girdwood <lgirdwood@...il.com>, linux-doc@...r.kernel.org
Subject: Re: [PATCH 1/2] MAINTAINERS: regulator: Add
Documentation/power/regulator/
On Tue, Nov 28, 2017 at 05:22:02AM +0100, Jonathan Neuschäfer wrote:
> On Sun, Nov 19, 2017 at 06:09:06AM +0100, Jonathan Neuschäfer wrote:
> > Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@....net>
> > ---
> > MAINTAINERS | 1 +
> > 1 file changed, 1 insertion(+)
>
> Ping.
>
> Should I resend this series with Cc: linux-doc@...r.kernel.org?
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" (489 bytes)
Powered by blists - more mailing lists