From: Hans de Goede <hdegoede@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: "Thomas Weißschuh" <linux@weissschuh.net>,
"Sebastian Reichel" <sre@kernel.org>,
linux-pm@vger.kernel.org,
"Stephen Rothwell" <sfr@canb.auug.org.au>
Subject: Re: [PATCH -next] power: supply: fix table problem in sysfs-class-power
Date: Tue, 18 Jan 2022 14:14:14 +0100 [thread overview]
Message-ID: <d8542235-01ff-e04f-84c6-53259ab845b9@redhat.com> (raw)
In-Reply-To: <20220118021522.1672-1-rdunlap@infradead.org>
Hi,
On 1/18/22 03:15, Randy Dunlap wrote:
> Add a bottom table border to complete the table format and prevent
> a documentation build warning.
>
> Documentation/ABI/testing/sysfs-class-power:459: WARNING: Malformed table.
> No bottom table border found.
>
> Fixes: 1b0b6cc8030d0 ("power: supply: add charge_behaviour attributes")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Thomas Weißschuh <linux@weissschuh.net>
> Cc: Hans de Goede <hdegoede@redhat.com>
> Cc: Sebastian Reichel <sre@kernel.org>
> Cc: linux-pm@vger.kernel.org
> Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Randy, thank you for the patch.
Sebastian, assuming you will merge 5.17-rc1 into your tree, this could
be merged through your tree (since this is a psy patch).
Since I've merged the original patch introducing this; and since I've
a bunch of other fixed lined up for 5.17 already, I would also
be happy to merge this through the pdx86 tree. Sebastian, please let
me know how you want to proceed with this ?
Regards,
Hans
> ---
> Documentation/ABI/testing/sysfs-class-power | 1 +
> 1 file changed, 1 insertion(+)
>
> --- linux-next-20220117.orig/Documentation/ABI/testing/sysfs-class-power
> +++ linux-next-20220117/Documentation/ABI/testing/sysfs-class-power
> @@ -468,6 +468,7 @@ Description:
> auto: Charge normally, respect thresholds
> inhibit-charge: Do not charge while AC is attached
> force-discharge: Force discharge while AC is attached
> + ================ ====================================
>
> What: /sys/class/power_supply/<supply_name>/technology
> Date: May 2007
>
prev parent reply other threads:[~2022-01-18 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 2:15 Randy Dunlap
2022-01-18 13:14 ` Hans de Goede [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=d8542235-01ff-e04f-84c6-53259ab845b9@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--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®