All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-iio@vger.kernel.org,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH] iio: accel: replace s64 __aligned(8) with aligned_s64
Date: Mon, 21 Oct 2024 19:32:54 +0100	[thread overview]
Message-ID: <20241021193254.61ea9048@jic23-huawei> (raw)
In-Reply-To: <ZxX-YXTOuYEb8AoY@smile.fi.intel.com>

On Mon, 21 Oct 2024 10:10:25 +0300
Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:

> On Sun, Oct 20, 2024 at 07:07:20PM +0100, 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.  
> 
> I agree on all your points.
> 
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> 

Applied given it's so trivial and 3 people already reviewed!

Thanks,

Jonathan

  reply	other threads:[~2024-10-21 18:33 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 [this message]
2024-10-21  7:41 ` Matti Vaittinen
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=20241021193254.61ea9048@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --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 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.