public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Nathan Chancellor <nathan@kernel.org>
Subject: Re: [RESEND PATCH 0/4] iio: Drop use of %hhx and %hx format strings
Date: Sat, 22 May 2021 19:20:31 +0100	[thread overview]
Message-ID: <20210522192031.26ecba8a@jic23-huawei> (raw)
In-Reply-To: <20210517125554.1463156-1-jic23@kernel.org>

On Mon, 17 May 2021 13:55:50 +0100
Jonathan Cameron <jic23@kernel.org> wrote:

> From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> 
> Resent because for some reason this didn't reach the mailing list
> (I'm not sure it reached anywhere at all!)
> 
> 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.

Series applied to the togreg branch of iio.git and pushed out as testing to
let 0-day poke at it before I push it out for linux-next.

Thanks,

Jonathan

> 
> Cc: Nathan Chancellor <nathan@kernel.org>
> Jonathan Cameron (4):
>   iio: imu: inv_mpu6050: Drop use of %hhx format string.
>   iio: light: si1133: Drop remaining uses of %hhx format string.
>   iio: light: si1145: Drop use of %hhx format specifier.
>   iio: chemical: sgp30: Drop use of %hx in format string.
> 
>  drivers/iio/chemical/sgp30.c               |  2 +-
>  drivers/iio/imu/inv_mpu6050/inv_mpu_core.c |  5 ++---
>  drivers/iio/light/si1133.c                 | 14 +++++++-------
>  drivers/iio/light/si1145.c                 | 10 +++++-----
>  4 files changed, 15 insertions(+), 16 deletions(-)
> 


  parent reply	other threads:[~2021-05-22 18:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17 12:55 [RESEND PATCH 0/4] iio: Drop use of %hhx and %hx format strings Jonathan Cameron
2021-05-17 12:55 ` [PATCH 1/4] iio: imu: inv_mpu6050: Drop use of %hhx format string Jonathan Cameron
2021-05-17 17:00   ` Nathan Chancellor
2021-05-17 12:55 ` [PATCH 2/4] iio: light: si1133: Drop remaining uses " Jonathan Cameron
2021-05-17 17:12   ` Nathan Chancellor
2021-05-17 12:55 ` [PATCH 3/4] iio: light: si1145: Drop use of %hhx format specifier Jonathan Cameron
2021-05-17 17:12   ` Nathan Chancellor
2021-05-17 12:55 ` [PATCH 4/4] iio: chemical: sgp30: Drop use of %hx in format string Jonathan Cameron
2021-05-17 17:13   ` Nathan Chancellor
2021-05-22 18:20 ` Jonathan Cameron [this message]
2021-06-03 18:08   ` [RESEND PATCH 0/4] iio: Drop use of %hhx and %hx format strings Jonathan Cameron

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=20210522192031.26ecba8a@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Jonathan.Cameron@huawei.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