linux-kernel - Re: [PATCH v2 1/2] iio: imu: inv

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHp75VciPdgt13GbWtH08_k-f6VHQ-e3aA+CibKNAS6WRWE9Ng@mail.gmail.com>
Date: Wed, 16 Apr 2025 16:06:39 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@....com>
Cc: Jonathan Cameron <jic23@...nel.org>, Lars-Peter Clausen <lars@...afoo.de>, 
	David Lechner <dlechner@...libre.com>, Nuno Sá <nuno.sa@...log.com>, 
	Andy Shevchenko <andy@...nel.org>, "linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>, 
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 1/2] iio: imu: inv_icm42600: add WoM support

On Wed, Apr 16, 2025 at 3:41 PM Jean-Baptiste Maneyrol
<Jean-Baptiste.Maneyrol@....com> wrote:
>
> Hello Andy,
>
> concerning usage of kernel types, my understanding was that we should conform to existing types usage in a driver. That's why I'm keeping the standard types instead of kernel ones. I could change them in the patch, but it would mix usage of both standard and kernel types.
>
> Another thing not related, by reading the coding style documentation I would think that for new driver we can use whatever we prefer between standard types and kernel types. Is it not the case?

It's not for the repositories Greg KH maintaining directly or indirectly:
https://lore.kernel.org/all/20170411140919.GC4388@kroah.com/

-- 
With Best Regards,
Andy Shevchenko