mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Daniel Lezcano <daniel.lezcano@kernel.org>,
	"open list:POWER SUPPLY CLASS/SUBSYSTEM and DRIVERS"
	<linux-pm@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] power: supply: Fix power limit documentation
Date: Fri, 11 Sep 2026 14:06:07 +0200	[thread overview]
Message-ID: <b84c1dac-3774-4d17-a1cd-90323c7faced@oss.qualcomm.com> (raw)
In-Reply-To: <aqHQPhfxUkJlQJmv@venus>

On 9/9/26 23:33, Sebastian Reichel wrote:
> Hi,
> 
> On Fri, Aug 21, 2026 at 05:39:49PM +0200, Daniel Lezcano wrote:
>> The documentation for the input current and voltage limits recommends
>> using those properties for problems that can be solved using a power
>> limit. This contradicts the recommendation to prefer input_power_limit
>> for such cases.
>>
>> Similarly, the input_power_limit documentation recommends using the
>> current or voltage limits for problems that can be solved with a power
>> limit, which conveys the opposite of the intended meaning.
>>
>> Fix the wording to clarify that input_power_limit should be preferred
>> whenever a power limit can address the problem, while current or
>> voltage limits should be used when it cannot.
> 
> Patch LGTM.
> 
>> Signed-off-by: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
>> Signed-off-by: Daniel Lezcano <daniel.lezcano@kernel.org>
> 
> Is this intentional?
No, my scripts again ...

Do you want me to resend or can you delete the kernel.org one ?

      reply	other threads:[~2026-09-11 12:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21 15:39 Daniel Lezcano
2026-09-09 21:33 ` Sebastian Reichel
2026-09-11 12:06   ` Daniel Lezcano [this message]

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=b84c1dac-3774-4d17-a1cd-90323c7faced@oss.qualcomm.com \
    --to=daniel.lezcano@oss.qualcomm.com \
    --cc=daniel.lezcano@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=sebastian.reichel@collabora.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

all inboxes | Powered by JetHome®