From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
"Srinivas Pandruvada" <srinivas.pandruvada@linux.intel.com>,
"Basavaraj Natikar" <Basavaraj.Natikar@amd.com>,
linux-input@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Jiri Kosina <jikos@kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Lorenzo Bianconi <lorenzo@kernel.org>
Subject: Re: [PATCH v2 2/3] iio: imu: st_lsm6dsx: Use aligned data type for timestamp
Date: Tue, 3 Sep 2024 21:09:24 +0300 [thread overview]
Message-ID: <ZtdQ1JsSlUxehQkm@smile.fi.intel.com> (raw)
In-Reply-To: <20240903180218.3640501-3-andriy.shevchenko@linux.intel.com>
On Tue, Sep 03, 2024 at 08:59:05PM +0300, Andy Shevchenko wrote:
> Use __aligned_s64 for the timestamp field.
Oh, heck. I forgot to change the commit message...
...
> - /* Ensure natural alignment of buffer elements */
...and for some reason this haven't been updated to be not removed.
I have updated locally, but will wait for other comments, maybe it's the only
problem and Jonathan can fix whilst applying.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-09-03 18:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 17:59 [PATCH v2 0/3] iio: Introduce and use aligned_s64 type Andy Shevchenko
2024-09-03 17:59 ` [PATCH v2 1/3] types: Complement the aligned types with signed 64-bit one Andy Shevchenko
2024-09-03 17:59 ` [PATCH v2 2/3] iio: imu: st_lsm6dsx: Use aligned data type for timestamp Andy Shevchenko
2024-09-03 18:09 ` Andy Shevchenko [this message]
2024-09-03 17:59 ` [PATCH v2 3/3] iio: hid-sensor: " Andy Shevchenko
2024-09-07 15:37 ` [PATCH v2 0/3] iio: Introduce and use aligned_s64 type Jonathan Cameron
2024-09-09 9:20 ` Andy Shevchenko
2024-09-09 19:01 ` Jonathan Cameron
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=ZtdQ1JsSlUxehQkm@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Basavaraj.Natikar@amd.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=jic23@kernel.org \
--cc=jikos@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=u.kleine-koenig@pengutronix.de \
/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.