From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: Manuel Ebner <manuelebner@mailbox.org>,
David Lechner <dlechner@baylibre.com>,
Nuno Sa <nuno.sa@analog.com>, Andy Shevchenko <andy@kernel.org>,
"open list:IIO SUBSYSTEM AND DRIVERS" <linux-iio@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation: ABI: testing: iio: minor cleanup
Date: Sun, 21 Jun 2026 14:55:44 +0100 [thread overview]
Message-ID: <20260621145544.23edacf3@jic23-huawei> (raw)
In-Reply-To: <ajJELTX_uJg0steQ@ashevche-desk.local>
On Wed, 17 Jun 2026 09:52:29 +0300
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
> On Fri, Jun 12, 2026 at 02:13:43PM +0200, Manuel Ebner wrote:
> > Add parenthesis and dashes.
>
> LGTM,
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
>
> ...
>
> > used to mask the buffer output value appropriately. The storagebits
> > value also specifies the data alignment. So s48/64>>2 will be a
> > - signed 48 bit integer stored in a 64 bit location aligned to a 64
> > - bit boundary. To obtain the clean value, shift right 2 and apply a
> > - mask to zero the top 16 bits of the result.
> > + signed 48-bit integer stored in a 64-bit location aligned to a
> > + 64-bit boundary. To obtain the clean value, shift right 2 and apply
> > + a mask to zero the top 16 bits of the result.
>
> We can reduce a churn by leaving 'a' as it was before (despite being long
> line). But I leave this exercise to Jonathan if he wants to.
True enough but I'm feeling lazy today (too hot and getting hotter :()
Applied.
Thanks,
Jonathan
>
prev parent reply other threads:[~2026-06-21 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 12:13 [PATCH] Documentation: ABI: testing: iio: minor cleanup Manuel Ebner
2026-06-17 6:52 ` Andy Shevchenko
2026-06-21 13:55 ` Jonathan Cameron [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=20260621145544.23edacf3@jic23-huawei \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manuelebner@mailbox.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