From: Jonathan Cameron <jic23@kernel.org>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Cc: <linux-iio@vger.kernel.org>, Arnd Bergmann <arnd@kernel.org>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
Joe Perches <joe@perches.com>,
Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH v2 0/4] iio: Drop use of %hhx and %hx format strings
Date: Wed, 9 Jun 2021 18:32:11 +0100 [thread overview]
Message-ID: <20210609183211.3427f59b@jic23-huawei> (raw)
In-Reply-To: <20210609140934.00002f44@Huawei.com>
On Wed, 9 Jun 2021 14:09:34 +0100
Jonathan Cameron <Jonathan.Cameron@Huawei.com> wrote:
> Hi All,
>
> Not quite sure how I managed to cc Nathan on the patches, but not the
> cover letter. Anyhow +Cc Nathan.
>
> @Nathan. I dropped the tags you gave to v1 as described below, but
> it's not a huge change. Very much appreciated if you could take a quick look.
Thanks for the quick turn around Nathan!
Applied to the togreg branch of iio.git and pushed out as testing for
the autobuilders to poke at.
Note I won't push this out as non rebasing for a few days so
still time to take additional reviews into account etc.
Jonathan
>
> Input from others also appreciated!
>
> Thanks,
>
> Jonathan
>
>
> On Thu, 3 Jun 2021 19:06:08 +0100
> Jonathan Cameron <jic23@kernel.org> wrote:
>
> > From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> >
> > A wrong use of one of these in
> > https://lore.kernel.org/linux-iio/20210514135927.2926482-1-arnd@kernel.org/
> > included a reference from Nathan to a patch discouraging the use of
> > these strings in general:
> > https://lore.kernel.org/lkml/CAHk-=wgoxnmsj8GEVFJSvTwdnWm8wVJthefNk2n6+4TC=20e0Q@mail.gmail.com/
> >
> > I did a quick grep and established we only have a few instances of these in
> > IIO anyway, so in the interests of avoiding those existing cases getting
> > cut and paste into new drivers, let's just clear them out now.
> >
> > Note that patch from Arnd is now also part of this series, due to the
> > length specifier related issue Joe raised.
> >
> > I have chosen to go with 0x%02x rather than %#04x as I find it more readable.
> >
> > V2:
> > Use 0x%02x (Joe Perches)
> > Include Arnd's original patch, modified for the above.
> >
> > Arnd Bergmann (1):
> > iio: si1133: fix format string warnings
> >
> > Jonathan Cameron (3):
> > iio: light: si1133: Drop remaining uses of %hhx format string.
> > iio: imu: inv_mpu6050: Drop use of %hhx format string.
> > iio: light: si1145: Drop use of %hhx format specifier.
> >
> > drivers/iio/imu/inv_mpu6050/inv_mpu_core.c | 5 ++---
> > drivers/iio/light/si1133.c | 18 +++++++++---------
> > drivers/iio/light/si1145.c | 10 +++++-----
> > 3 files changed, 16 insertions(+), 17 deletions(-)
> >
>
prev parent reply other threads:[~2021-06-09 17:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 18:06 [PATCH v2 0/4] iio: Drop use of %hhx and %hx format strings Jonathan Cameron
2021-06-03 18:06 ` [PATCH v2 1/4] iio: si1133: fix format string warnings Jonathan Cameron
2021-06-09 15:27 ` Nathan Chancellor
2021-06-03 18:06 ` [PATCH v2 2/4] iio: light: si1133: Drop remaining uses of %hhx format string Jonathan Cameron
2021-06-09 15:27 ` Nathan Chancellor
2021-06-03 18:06 ` [PATCH v2 3/4] iio: imu: inv_mpu6050: Drop use " Jonathan Cameron
2021-06-09 15:28 ` Nathan Chancellor
2021-06-03 18:06 ` [PATCH v2 4/4] iio: light: si1145: Drop use of %hhx format specifier Jonathan Cameron
2021-06-09 15:29 ` Nathan Chancellor
2021-06-03 18:58 ` General kernel misuse of vsnprintf SPECIAL %#<foo> (was: Re: [PATCH v2 0/4] iio: Drop use of %hhx and %hx format strings) Joe Perches
2021-06-03 19:25 ` Jonathan Cameron
2021-06-03 19:34 ` Joe Perches
2021-06-04 8:27 ` Jonathan Cameron
2021-06-09 13:09 ` [PATCH v2 0/4] iio: Drop use of %hhx and %hx format strings Jonathan Cameron
2021-06-09 17:32 ` 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=20210609183211.3427f59b@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@Huawei.com \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@kernel.org \
--cc=joe@perches.com \
--cc=linux-iio@vger.kernel.org \
--cc=nathan@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