mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fiona Klute <fiona.klute@gmx.de>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Roan van Dijk" <roan@protonic.nl>,
	linux-iio@vger.kernel.org,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: chemical: scd4x: expose timestamp channel
Date: Mon, 22 Dec 2025 17:39:35 +0100	[thread overview]
Message-ID: <08059e1e-4e6c-4493-8c00-294b50fad821@gmx.de> (raw)
In-Reply-To: <20251221180508.252bd6d9@jic23-huawei>

Am 21.12.25 um 19:05 schrieb Jonathan Cameron:
> On Thu, 18 Dec 2025 16:12:05 +0100
> Fiona Klute <fiona.klute@gmx.de> wrote:
> 
>> Timestamps were already written to the buffer in
>> scd4x_trigger_handler(), this patch makes them available as a channel.
>>
>> Signed-off-by: Fiona Klute <fiona.klute@gmx.de>
> Applied to the togreg branch of iio.git. Initially pushed out as testing
> to let 0-day have a brief look at it.
Thank you! Could you also pick my channel endianness fix for the scd4x 
driver [1]? The patches apply independently, but timestamps aren't going 
to be very useful as long as the data that goes with them is incorrect. 
Or does that need to go via a different tree as a bugfix?

Best regards,
Fiona


[1] 
https://lore.kernel.org/linux-iio/20251213163226.1678707-1-fiona.klute@gmx.de/T/


      reply	other threads:[~2025-12-22 16:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-18 15:12 Fiona Klute
2025-12-21 18:05 ` Jonathan Cameron
2025-12-22 16:39   ` Fiona Klute [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=08059e1e-4e6c-4493-8c00-294b50fad821@gmx.de \
    --to=fiona.klute@gmx.de \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=roan@protonic.nl \
    /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

all inboxes | Powered by JetHome®