Linux IIO development
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@tdk.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] iio: imu: inv_icm42600: add WoM support
Date: Wed, 16 Apr 2025 18:28:23 +0300	[thread overview]
Message-ID: <Z__Ml-NvzgC8-ltv@smile.fi.intel.com> (raw)
In-Reply-To: <FR3P281MB1757AA98627383BC411A35F5CEBD2@FR3P281MB1757.DEUP281.PROD.OUTLOOK.COM>

On Wed, Apr 16, 2025 at 02:40:50PM +0000, Jean-Baptiste Maneyrol wrote:
> OK, understood.
> 
> But for this particular patch, do I need to stay consistent with the existing
> driver by keeping the standard type or use kernel types and mix with standard
> types?

Yes, consistency with the existing code is priority, if the change is a fix.
If it's a feature, better to clean up first (i.e. switch the types elsewhere)
and then add a new feature.

> From: Andy Shevchenko <andy.shevchenko@gmail.com>
> Sent: Wednesday, April 16, 2025 15:06
> To: Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@tdk.com>
> On Wed, Apr 16, 2025 at 3:41 PM Jean-Baptiste Maneyrol
> <Jean-Baptiste.Maneyrol@tdk.com> wrote:
> >
> > 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://urldefense.com/v3/__https://lore.kernel.org/all/20170411140919.GC4388@kroah.com/__;!!FtrhtPsWDhZ6tw!ACor8Q-WyU0CorzLpw0OtWqNk59Wn2Z_s7KKOZuNnglKBzN4jTqb3c6oea83KLER97bFxkEIgSl8_IcKHTxvaRKCUwVCP5wunvo$[lore[.]kernel[.]org]

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-04-16 15:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 14:47 [PATCH v2 0/2] Add support for WoM (Wake-on-Motion) feature Jean-Baptiste Maneyrol via B4 Relay
2025-04-15 14:47 ` [PATCH v2 1/2] iio: imu: inv_icm42600: add WoM support Jean-Baptiste Maneyrol via B4 Relay
2025-04-15 18:18   ` Andy Shevchenko
2025-04-16 12:40     ` Jean-Baptiste Maneyrol
2025-04-16 13:06       ` Andy Shevchenko
2025-04-16 14:40         ` Jean-Baptiste Maneyrol
2025-04-16 15:28           ` Andy Shevchenko [this message]
2025-04-17 14:25     ` Jean-Baptiste Maneyrol
2025-04-17 16:10       ` Andy Shevchenko
2025-04-15 14:47 ` [PATCH v2 2/2] iio: imu: inv_icm42600: add wakeup functionality for Wake-on-Motion Jean-Baptiste Maneyrol via B4 Relay
2025-04-15 18: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=Z__Ml-NvzgC8-ltv@smile.fi.intel.com \
    --to=andy.shevchenko@gmail.com \
    --cc=Jean-Baptiste.Maneyrol@tdk.com \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --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