From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
"Jean-Baptiste Maneyrol" <jean-baptiste.maneyrol@tdk.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>
Subject: Re: [PATCH v1 1/1] iio: imu: inv_icm42600: Convert to uXX and sXX integer types
Date: Tue, 3 Feb 2026 13:21:13 +0200 [thread overview]
Message-ID: <aYHaKYWNbrZchDn-@smile.fi.intel.com> (raw)
In-Reply-To: <20251115185001.01f2b148@jic23-huawei>
On Sat, Nov 15, 2025 at 06:50:01PM +0000, Jonathan Cameron wrote:
> On Sun, 9 Nov 2025 20:24:36 +0100
> Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
>
> > The driver code is full of intXX_t and uintXX_t types which is
> > not the pattern we use in the IIO subsystem. Switch the driver
> > to use kernel internal types for that. No functional changes.
> No problem with the change but this description made me think
> that this was going to be a huge patch touching lots of instances.
>
> Probably needs a rewrite to not say 'full of' :)
Can you tweak that whilst applying, please?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-02-03 11:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-09 19:24 [PATCH v1 1/1] iio: imu: inv_icm42600: Convert to uXX and sXX integer types Andy Shevchenko
2025-11-09 19:33 ` Andy Shevchenko
2025-11-15 18:48 ` Jonathan Cameron
2025-11-15 18:50 ` Jonathan Cameron
2026-02-03 11:21 ` Andy Shevchenko [this message]
2026-02-05 19:29 ` Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2025-06-16 9:03 Andy Shevchenko
2025-06-16 14:16 ` Jean-Baptiste Maneyrol
2025-06-16 14:33 ` Andy Shevchenko
2025-06-17 14:43 ` Jean-Baptiste Maneyrol
2025-06-17 18:33 ` Andy Shevchenko
2025-06-21 17:13 ` Jonathan Cameron
2025-06-23 6:39 ` 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=aYHaKYWNbrZchDn-@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jean-baptiste.maneyrol@tdk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.