From: Dhruva Gole <d-gole@ti.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: <linux-kernel@vger.kernel.org>,
Sebastian Reichel <sre@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Pavel Machek <pavel@kernel.org>,
Jonathan Corbet <corbet@lwn.net>, <linux-doc@vger.kernel.org>,
<linux-pm@vger.kernel.org>
Subject: Re: [PATCH] docs: power: clean up power_supply_class.rst
Date: Tue, 14 Oct 2025 10:57:43 +0530 [thread overview]
Message-ID: <20251014052743.7epupfxrymbq3eu6@lcpd911> (raw)
In-Reply-To: <20251014031617.764429-1-rdunlap@infradead.org>
On Oct 13, 2025 at 20:16:15 -0700, Randy Dunlap wrote:
> Clean up grammar, punctuation, etc., in the power supply class
> documentation.
>
> Add article adjectives where needed.
> Hyphenate some adjectives.
> Fix punctuation.
> Fix some verb usage (singular/plural).
> Fix run-on sentences.
> Add "is" in a few places.
> Change "QA" to "Q&A".
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Cc: Sebastian Reichel <sre@kernel.org>
> Cc: "Rafael J. Wysocki" <rafael@kernel.org>
> Cc: Len Brown <lenb@kernel.org>
> Cc: Pavel Machek <pavel@kernel.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
> Cc: linux-pm@vger.kernel.org
> ---
> Documentation/power/power_supply_class.rst | 84 +++++++++----------
> 1 file changed, 42 insertions(+), 42 deletions(-)
>
> --- linux-next-20251013.orig/Documentation/power/power_supply_class.rst
> +++ linux-next-20251013/Documentation/power/power_supply_class.rst
> @@ -7,35 +7,35 @@ Synopsis
> Power supply class used to represent battery, UPS, AC or DC power supply
> properties to user-space.
>
> -It defines core set of attributes, which should be applicable to (almost)
> +It defines a core set of attributes which should be applicable to (almost)
> every power supply out there. Attributes are available via sysfs and uevent
> interfaces.
>
> -Each attribute has well defined meaning, up to unit of measure used. While
> +Each attribute has a well-defined meaning, up to unit of measure used. While
Not a native English speaker but see if this makes sense?
up to "the" unit of measure used.
> the attributes provided are believed to be universally applicable to any
> power supply, specific monitoring hardware may not be able to provide them
> all, so any of them may be skipped.
>
> -Power supply class is extensible, and allows to define drivers own attributes.
> -The core attribute set is subject to the standard Linux evolution (i.e.
> -if it will be found that some attribute is applicable to many power supply
> -types or their drivers, it can be added to the core set).
> +The power supply class is extensible and allows drivers to define their own
> +attributes. The core attribute set is subject to the standard Linux evolution
> +(i.e., if it will be found that some attribute is applicable to many power
Reword as follows:
i.e., if some attribute is found to be applicable to many power supply types
> +supply types or their drivers, it can be added to the core set).
>
> -It also integrates with LED framework, for the purpose of providing
> +It also integrates with the LED framework, for the purpose of providing
> typically expected feedback of battery charging/fully charged status and
> AC/USB power supply online status. (Note that specific details of the
> indication (including whether to use it at all) are fully controllable by
> -user and/or specific machine defaults, per design principles of LED
> -framework).
> +user and/or specific machine defaults, per design principles of the LED
> +framework.)
>
With that, if you plan to respin feel free to include:
Reviewed-by: Dhruva Gole <d-gole@ti.com>
--
Best regards,
Dhruva Gole
Texas Instruments Incorporated
next prev parent reply other threads:[~2025-10-14 5:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 3:16 Randy Dunlap
2025-10-14 5:27 ` Dhruva Gole [this message]
2025-10-14 5:49 ` Randy Dunlap
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=20251014052743.7epupfxrymbq3eu6@lcpd911 \
--to=d-gole@ti.com \
--cc=corbet@lwn.net \
--cc=lenb@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=sre@kernel.org \
/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®