mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Manuel Ebner <manuelebner@mailbox.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: David Lechner <dlechner@baylibre.com>,
	Nuno Sa <nuno.sa@analog.com>,  Andy Shevchenko <andy@kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	 linux-iio@vger.kernel.org
Subject: Re: [PATCH] Documentation: ABI: fix brackets and bracelets
Date: Thu, 11 Jun 2026 13:54:04 +0200	[thread overview]
Message-ID: <54d15f70bd8ec76eea0a792ca701195b8472ee2a.camel@mailbox.org> (raw)
In-Reply-To: <20260611104643.2a5ed6c2@jic23-huawei>

On Thu, 2026-06-11 at 10:46 +0100, Jonathan Cameron wrote:
> On Thu, 11 Jun 2026 10:56:21 +0200
> Manuel Ebner <manuelebner@mailbox.org> wrote:
> 
> > Fix missing and needless brackets
> > Fix missing bracelets
> > 
> > Signed-off-by: Manuel Ebner <manuelebner@mailbox.org>
> > ---
> >  Documentation/ABI/stable/sysfs-class-infiniband      | 4 ++--
> >  Documentation/ABI/testing/sysfs-bus-iio              | 4 ++--
> >  Documentation/ABI/testing/sysfs-bus-iio-adc-ad7192   | 2 +-
> 
> Take a look at hos this stuff is routed into upstream.  Each 
> subsystem 'owns' their own documentation.  So this needs splitting up
> on a per subsystem basis.  I'll also note that you've only +CC IIO folk
> so you aren't going to get much review on the rest!

I send it to the addresses get_maintainer returned, except the git blame
ones. How can I find out who to send this to?

> A few comments inline.
> 
> >  Documentation/ABI/testing/sysfs-firmware-dmi-entries | 2 +-
> >  Documentation/ABI/testing/sysfs-firmware-gsmi        | 2 +-
> >  Documentation/ABI/testing/sysfs-uevent               | 2 +-
> >  6 files changed, 8 insertions(+), 8 deletions(-)
> > 
> > diff --git a/Documentation/ABI/stable/sysfs-class-infiniband
> > b/Documentation/ABI/stable/sysfs-class-infiniband
> > index 694f23a03a28..e48a0d2fb4e5 100644
> > --- a/Documentation/ABI/stable/sysfs-class-infiniband
> > +++ b/Documentation/ABI/stable/sysfs-class-infiniband
> > @@ -157,8 +157,8 @@ Description:
> >  		all VLs from this port. This may include packets with errors.
> >  		This is 64 bit counter.
> >  
> > -		port_rcv_packets: (RO) Total number of packets (this may include
> > -		packets containing Errors. This is 64 bit counter.
> > +		port_rcv_packets: (RO) Total number of packets, this may include
> > +		packets containing Errors. This is a 64 bit counter.
> Comma doesn't feel like the right choice here.  Perhaps,
> 
> 		port_rc_packets: (RO) Total number of packets. May include
> 		packets containing Errors. This is a 64 bit counter.
> 
> Or just add the closing bracket.

will do this.

> >  
> >  		link_downed: (RO) Total number of times the Port Training state
> >  		machine has failed the link error recovery process and downed
> > 
> > diff --git a/Documentation/ABI/testing/sysfs-bus-iio-adc-ad7192
> > b/Documentation/ABI/testing/sysfs-bus-iio-adc-ad7192
> > index 28be1cabf112..108ea0abbdb6 100644
> > --- a/Documentation/ABI/testing/sysfs-bus-iio-adc-ad7192
> > +++ b/Documentation/ABI/testing/sysfs-bus-iio-adc-ad7192
> > @@ -16,7 +16,7 @@ Description:
> >  		In bridge applications, such as strain gauges and load cells,
> >  		the bridge itself consumes the majority of the current in the
> >  		system. To minimize the current consumption of the system,
> > -		the bridge can be disconnected (when it is not being used
> > +		the bridge can be disconnected when it is not being used
> >  		using the bridge_switch_en attribute.
> 
> I think intent would be better reflected here by adding the closing )
> That last bit is kind of a 'by the way' rather than the dominant point of
> the sentence.

		system. To minimize the current consumption of the system,
-		the bridge can be disconnected (when it is not being used
+		the bridge can be disconnected (when it is not being used)
 		using the bridge_switch_en attribute.
like this?

> 
> >  
> >  What:		/sys/bus/iio/devices/iio:deviceX/in_voltage2-voltage2_shorted_raw
> 
> > diff --git a/Documentation/ABI/testing/sysfs-firmware-gsmi
> > b/Documentation/ABI/testing/sysfs-firmware-gsmi
> > index 7a558354c1ee..88ca75d323d1 100644
> > --- a/Documentation/ABI/testing/sysfs-firmware-gsmi
> > +++ b/Documentation/ABI/testing/sysfs-firmware-gsmi
> > @@ -18,7 +18,7 @@ Description:
> >  
> >  		/sys/firmware/gsmi/vars:
> >  
> > -			This directory has the same layout (and
> > +			This directory has the same layout and
> >  			underlying implementation as /sys/firmware/efi/vars.
> >  			See `Documentation/ABI/*/sysfs-firmware-efi-vars`
> >  			for more information on how to interact with
> I think I'd add the bracket after implementation as this file is about ABI
> so that's less important than the rest of the sentence.

			This directory has the same layout (and
- 			underlying implementation as /sys/firmware/efi/vars.
+ 			underlying implementation) as /sys/firmware/efi/vars.
 			See `Documentation/ABI/*/sysfs-firmware-efi-vars`
 			for more information on how to interact with

like this?

Thanks 
 manuel

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-11  8:56 Manuel Ebner
2026-06-11  9:46 ` Jonathan Cameron
2026-06-11 11:54   ` Manuel Ebner [this message]
2026-06-11 16:15     ` Jonathan Cameron
2026-06-11 18:46       ` Andy Shevchenko
2026-06-11 18:44 ` Andy Shevchenko

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=54d15f70bd8ec76eea0a792ca701195b8472ee2a.camel@mailbox.org \
    --to=manuelebner@mailbox.org \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.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®