From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "Nuno Sá" <noname.nuno@gmail.com>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: adc: ad7606: explicit timestamp alignment
Date: Mon, 5 May 2025 16:14:02 +0100 [thread overview]
Message-ID: <20250505161402.48da1ba7@jic23-huawei> (raw)
In-Reply-To: <efe160b5-5d91-4892-a0d6-ef73116fe071@baylibre.com>
On Mon, 5 May 2025 08:57:29 -0500
David Lechner <dlechner@baylibre.com> wrote:
> On 5/4/25 9:55 AM, Jonathan Cameron wrote:
> > On Tue, 29 Apr 2025 14:01:54 +0100
> > Nuno Sá <noname.nuno@gmail.com> wrote:
> >
> >> On Mon, 2025-04-28 at 21:17 -0500, David Lechner wrote:
> >>> Use struct with aligned_s64 timestamp to make timestamp alignment
> >>> explicit. Technically, what we have works because for all known
> >>> architectures, IIO_DMA_MINALIGN is a multiple of __alignof__(s64).
> >>> But this way, we don't have to make people read the comments to know
> >>> why there are extra elements in each buffer.
> >>>
> >>> ---
> >>
> >> Reviewed-by: Nuno Sá <nuno.sa@analog.com>
> > Applied to the togreg branch of iio.git and pushed out as testing
> > for all the normal reasons.
> >
> Not sure how we all managed to this, but this is missing:
>
> Signed-off-by: David Lechner <dlechner@baylibre.com>
>
Oops.
Added.
prev parent reply other threads:[~2025-05-05 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 2:17 [PATCH] iio: adc: ad7606: explicit timestamp alignment David Lechner
2025-04-29 13:01 ` Nuno Sá
2025-05-04 14:55 ` Jonathan Cameron
2025-05-05 13:57 ` David Lechner
2025-05-05 15:14 ` Jonathan Cameron [this message]
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=20250505161402.48da1ba7@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noname.nuno@gmail.com \
--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