From: Kory Maincent <kory.maincent@bootlin.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Oleksij Rempel <o.rempel@pengutronix.de>,
kernel@pengutronix.de
Subject: Re: [PATCH v2 0/2] Add support for power budget
Date: Fri, 17 Jan 2025 14:57:10 +0100 [thread overview]
Message-ID: <20250117145710.36ab4cc9@kmaincent-XPS-13-7390> (raw)
In-Reply-To: <b1ab3115-e84f-4b17-bda2-c76666ba6ac3@sirena.org.uk>
On Fri, 17 Jan 2025 13:48:54 +0000
Mark Brown <broonie@kernel.org> wrote:
> On Fri, Jan 17, 2025 at 01:09:36PM +0100, Kory Maincent wrote:
> > On Wed, 15 Jan 2025 15:41:56 +0100
>
> > > In preparation for future support of PSE budget evaluation strategy and
> > > power management, we need the power budget value of the power supply.
>
> > Is there hope this will be merged before the merge window?
>
> 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.
Ok, dully noted! Sorry for the noise!
Regards,
--
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-01-17 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 14:41 [PATCH v2 0/2] Add support for power budget Kory Maincent
2025-01-15 14:41 ` [PATCH v2 1/2] regulator: " Kory Maincent
2025-01-15 14:41 ` [PATCH v2 2/2] regulator: dt-bindings: Add regulator-power-budget-milliwatt property Kory Maincent
2025-01-20 18:20 ` Conor Dooley
2025-01-17 12:09 ` [PATCH v2 0/2] Add support for power budget Kory Maincent
2025-01-17 13:48 ` Mark Brown
2025-01-17 13:57 ` Kory Maincent [this message]
2025-01-17 22:52 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250117145710.36ab4cc9@kmaincent-XPS-13-7390 \
--to=kory.maincent@bootlin.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox