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] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240217162014.17033d64@jic23-huawei>
Date: Sat, 17 Feb 2024 16:20:14 +0000
From: Jonathan Cameron <jic23@...nel.org>
To: David Lechner <dlechner@...libre.com>
Cc: linux-iio@...r.kernel.org, Rob Herring <robh+dt@...nel.org>, Krzysztof
 Kozlowski <krzysztof.kozlowski+dt@...aro.org>, Conor Dooley
 <conor+dt@...nel.org>, Michael Hennerich <michael.hennerich@...log.com>,
 Nuno Sá <nuno.sa@...log.com>, Liam Girdwood
 <lgirdwood@...il.com>, Mark Brown <broonie@...nel.org>,
 linux-kernel@...r.kernel.org, Stefan Popa <stefan.popa@...log.com>,
 devicetree@...r.kernel.org, Julien Stephan <jstephan@...libre.com>
Subject: Re: [PATCH v4 2/2] iio: adc: ad7380: new driver for AD7380 ADCs

On Fri, 16 Feb 2024 14:34:01 -0600
David Lechner <dlechner@...libre.com> wrote:

> On Wed, Jan 10, 2024 at 2:29 PM David Lechner <dlechner@...libre.com> wrote:
> >
> > This adds a new driver for the AD7380 family ADCs.
> >
> > The driver currently implements basic support for the AD7380, AD7381,
> > AD7383, and AD7384 2-channel differential ADCs. Support for additional
> > single-ended and 4-channel chips that use the same register map as well
> > as additional features of the chip will be added in future patches.
> >  
> 
> Hi Jonathan,
> 
> We have some additional features to add to this driver we are working
> on that look like they might affect userspace. Can we hold off on
> sending this one to Greg for 6.9? That way we will have more time to
> sort that out without having to worry about breaking userspace.

Ok. Hopefully rebasing my tree won't cause others too many downstream
problems. Generally I only do this if there is an invalid tag or similar
that must be fixed.  There is normally a window of a weekish
between me picking it up and pushing out for linux-next to pick up and
hopefully issues like this get spotted in that window.
Ah well, sometimes things don't work out how we would like them to.

Dropped the 3 patches (original driver and a fix) from the togreg branch.

Jonathan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ