linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@tdk.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Jonathan Cameron" <jic23@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, 17 Jun 2025 14:43:36 +0000	[thread overview]
Message-ID: <FR3P281MB175775DBE90C5469637F3C66CE73A@FR3P281MB1757.DEUP281.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAHp75Ve68H448v3Tgv930yoMYCCKVC3kefuP+Rermj7SaiP41g@mail.gmail.com>

>
>________________________________________
>From: Andy Shevchenko <andy.shevchenko@gmail.com>
>Sent: Monday, June 16, 2025 16:33
>To: Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@tdk.com>
>Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>; Jonathan Cameron <Jonathan.Cameron@huawei.com>; linux-iio@vger.kernel.org <linux-iio@vger.kernel.org>; linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>; Jonathan Cameron <jic23@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
> 
>This Message Is From an External Sender
>This message came from outside your organization.
> 
>On Mon, Jun 16, 2025 at 5:16 PM Jean-Baptiste Maneyrol
><Jean-Baptiste.Maneyrol@tdk.com> wrote:
>
>> thanks a lot for having done all the work.
>
>Please, avoid top-posting!
>
>> Do you think it is possible to add a fixes tag so it can be backported to ease automatic backport of further patches?
>> Otherwise for sure all further fixes will have to be backported manually.
>
>The idea behind the series that it may depend on some kind of
>cleanups. In such a case (according to Greg KH) no need to have Fixes
>tag on a cleanup, because it's confusing. On the contrary the
>infrastructure for stable kernels will catch this up. You need to
>follow the Documentation on how to submit for stable (basically the
>main hint is to use stable@ in the Cc line _inside_ the commit
>message, as a tag).
>
>> 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.
>>
>> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>> ---
>>
>> As noted before the pattern is used in less than 10% files in IIO,
>> So it's safe to assume that IIO prefers uXX/sXX types over C99 ones.
>
>-- 
>With Best Regards,
>Andy Shevchenko
>

Hello Andy,

it is good for me if we can add Cc to stable.
I don't know if I need to add the Cc tag here or when a fixed patch will
require the rework. In doubt, here it is.

Acked-by: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
Cc: stable@vger.kernel.org

Thanks,
JB

  reply	other threads:[~2025-06-17 14:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16  9:03 [PATCH v1 1/1] iio: imu: inv_icm42600: Convert to uXX and sXX integer types 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 [this message]
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=FR3P281MB175775DBE90C5469637F3C66CE73A@FR3P281MB1757.DEUP281.PROD.OUTLOOK.COM \
    --to=jean-baptiste.maneyrol@tdk.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).