Linux IIO development
 help / color / mirror / Atom feed
From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>, linux-iio@vger.kernel.org
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH] iio: accel: replace s64 __aligned(8) with aligned_s64
Date: Mon, 21 Oct 2024 10:41:31 +0300	[thread overview]
Message-ID: <e52c9571-098f-46d5-95de-fbcfabb617a3@gmail.com> (raw)
In-Reply-To: <20241020180720.496327-1-jic23@kernel.org>

On 20/10/2024 21:07, Jonathan Cameron wrote:
> From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> 
> e4ca0e59c394 ("types: Complement the aligned types with signed 64-bit one")
> introduced aligned_s64. Use it for all IIO accelerometer drivers.
> 
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> 
> ---
> 
> I debated whether to split this up by driver by the time we've done all IIO
> drivers that will be a very large number of trivial patches.
> 
> The changes are minor enough that they shouldn't present much of a
> backporting challenge if needed for future fixes etc.
> 
> I'm find splitting them up if people prefer.
> Next on my list is to look at adding runtime checks that the buffers
> containing these timestamps are big enough but I want this out of the
> way first.

Makes sense to me.

> Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
>   drivers/iio/accel/kionix-kx022a.c   | 3 ++-
>   drivers/iio/accel/kxcjk-1013.c      | 3 ++-
>   drivers/iio/accel/kxsd9.c           | 3 ++-

For the Kionix/ROHM seensors,
Reviewed-by: Matti Vaittinen <mazziesaccount@gmail.com>


Yours,
	-- Matti

  parent reply	other threads:[~2024-10-21  7:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-20 18:07 [PATCH] iio: accel: replace s64 __aligned(8) with aligned_s64 Jonathan Cameron
2024-10-21  7:10 ` Andy Shevchenko
2024-10-21 18:32   ` Jonathan Cameron
2024-10-21  7:41 ` Matti Vaittinen [this message]
2024-10-21  8:15 ` Nuno Sá
2024-10-21  8:18 ` Nuno Sá
2024-10-23 12:44 ` Dmitry Rokosov

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=e52c9571-098f-46d5-95de-fbcfabb617a3@gmail.com \
    --to=mazziesaccount@gmail.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.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