[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a979db13-9ced-487a-ad35-47d6ea50ddf2@sirena.org.uk>
Date: Mon, 28 Oct 2024 15:39:47 +0000
From: Mark Brown <broonie@...nel.org>
To: Mikhail Rudenko <mike.rudenko@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-rockchip@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org,
Liam Girdwood <lgirdwood@...il.com>, Alex Bee <knaerzche@...il.com>,
Lee Jones <lee@...nel.org>, Quentin Schulz <foss+kernel@...il.net>,
Linus Walleij <linus.walleij@...aro.org>,
Chris Zhong <zyw@...k-chips.com>,
Zhang Qing <zhangqing@...k-chips.com>
Subject: Re: [PATCH] regulator: rk808: Add apply_bit for BUCK3 on RK809
On Mon, Oct 28, 2024 at 06:20:55PM +0300, Mikhail Rudenko wrote:
> Gentle ping.
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.
Please don't top post, reply in line with needed context. This allows
readers to readily follow the flow of conversation and understand what
you are talking about and also helps ensure that everything in the
discussion is being addressed.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists