[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZO3wMlze3HRkkoMY@smile.fi.intel.com>
Date: Tue, 29 Aug 2023 16:18:42 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Jonathan Cameron <jic23@...nel.org>
Cc: Jonathan Cameron <Jonathan.Cameron@...wei.com>,
Lorenzo Bianconi <lorenzo@...nel.org>,
Philipp Jungkamp <p.jungkamp@....net>,
Peter Zijlstra <peterz@...radead.org>,
linux-input@...r.kernel.org, linux-iio@...r.kernel.org,
linux-kernel@...r.kernel.org, Jiri Kosina <jikos@...nel.org>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
Lars-Peter Clausen <lars@...afoo.de>
Subject: Re: [PATCH v1 2/3] iio: imu: st_lsm6dsx: Use aligned data type for
timestamp
On Mon, Aug 28, 2023 at 05:03:41PM +0100, Jonathan Cameron wrote:
> On Tue, 15 Aug 2023 18:40:26 +0300
> Andy Shevchenko <andriy.shevchenko@...ux.intel.com> wrote:
...
> > struct {
> > __le16 channels[3];
> > - s64 ts __aligned(8);
> > + __aligned_s64 ts;
>
> aligned_s64 as it's internal to the kernel?
Either works, but strictly speaking you are right, better no underscored
variant.
> > } scan[ST_LSM6DSX_ID_MAX];
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists