[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6e64ac1b-ce91-414a-9a39-50480971ceca@sirena.org.uk>
Date: Thu, 16 Mar 2023 11:21:56 +0000
From: Mark Brown <broonie@...nel.org>
To: Sebastian Reichel <sebastian.reichel@...labora.com>
Cc: Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org,
Lee Jones <lee@...nel.org>
Subject: Re: [PATCHv7 10/11] regulator: expose regulator_find_closest_bigger
On Thu, Mar 16, 2023 at 02:34:53AM +0100, Sebastian Reichel wrote:
> On Tue, Mar 07, 2023 at 04:36:16PM +0100, Sebastian Reichel wrote:
> > Expose and document the table lookup logic used by
> > regulator_set_ramp_delay_regmap, so that it can be
> > reused for devices that cannot be configured via
> > regulator_set_ramp_delay_regmap.
> >
> > Signed-off-by: Sebastian Reichel <sebastian.reichel@...labora.com>
> Can you please Ack and the following patch?
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.
> (they needs to go through MFD tree)
That seems entirely non-obvious from the subject.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists