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: <aYW7lt26Tn-6Fgno@smile.fi.intel.com>
Date: Fri, 6 Feb 2026 11:59:50 +0200
From: Andy Shevchenko <andriy.shevchenko@...el.com>
To: Oleksij Rempel <o.rempel@...gutronix.de>
Cc: Jonathan Cameron <jic23@...nel.org>, Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>, kernel@...gutronix.de,
	linux-kernel@...r.kernel.org, linux-iio@...r.kernel.org,
	devicetree@...r.kernel.org, Andy Shevchenko <andy@...nel.org>,
	David Lechner <dlechner@...libre.com>,
	Nuno Sá <nuno.sa@...log.com>,
	David Jander <david@...tonic.nl>
Subject: Re: [PATCH v4 06/13] iio: dac: ds4424: use device match data for
 chip info

On Fri, Feb 06, 2026 at 08:57:07AM +0100, Oleksij Rempel wrote:
> On Thu, Feb 05, 2026 at 08:43:25PM +0000, Jonathan Cameron wrote:
> > On Tue, 3 Feb 2026 16:56:00 +0200
> > Andy Shevchenko <andriy.shevchenko@...el.com> wrote:

...

> > > Just do not introduce that change (change of the ->name field) in the original
> > > patch, in that case no revert churn would be needed.
> > > 
> > I think this got dealt with in discussion of next version but
> > safest route is just have an extra copy of the name in the
> > chip_info structure.  Then we know it's stable against different
> > firmware types etc.
> 
> Something like this?

Yes, but make it in the patch that introduces DT support.

-- 
With Best Regards,
Andy Shevchenko



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ