lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <08059e1e-4e6c-4493-8c00-294b50fad821@gmx.de>
Date: Mon, 22 Dec 2025 17:39:35 +0100
From: Fiona Klute <fiona.klute@....de>
To: Jonathan Cameron <jic23@...nel.org>
Cc: Roan van Dijk <roan@...tonic.nl>, linux-iio@...r.kernel.org,
 David Lechner <dlechner@...libre.com>, Nuno Sá
 <nuno.sa@...log.com>, Andy Shevchenko <andy@...nel.org>,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] iio: chemical: scd4x: expose timestamp channel

Am 21.12.25 um 19:05 schrieb Jonathan Cameron:
> On Thu, 18 Dec 2025 16:12:05 +0100
> Fiona Klute <fiona.klute@....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@....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/


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ