linux-kernel - Re: [PATCH] iio: amplifiers: ad8366: make ad8366

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: <20250629180339.760c189f@jic23-huawei>
Date: Sun, 29 Jun 2025 18:03:39 +0100
From: Jonathan Cameron <jic23@...nel.org>
To: David Lechner <dlechner@...libre.com>
Cc: Lars-Peter Clausen <lars@...afoo.de>, Michael Hennerich
 <Michael.Hennerich@...log.com>, Nuno Sá <nuno.sa@...log.com>,
 Andy Shevchenko <andy@...nel.org>, linux-iio@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] iio: amplifiers: ad8366: make ad8366_info const

On Sat, 28 Jun 2025 12:05:03 -0500
David Lechner <dlechner@...libre.com> wrote:

> On 6/28/25 12:01 PM, David Lechner wrote:
> > Add const qualifier to struct ad8366_info ad8366_infos[]. This
> > is read-only data so it can be made const.
> > 
> > Signed-off-by: David Lechner <dlechner@...libre.com>
> > ---
> > I looked into dropping use of the chip info array in this one, but
> > removing it isn't trivial. There are several switch statements that
> > are using the chip ID still. So we'll save that for another day.
> > ---
> >  drivers/iio/amplifiers/ad8366.c | 6 +++---  
> 
> Replying with the correct subject. I missed updating the prefix
> from a copied commit message.
> 
> Should be `iio: amplifiers: ad8366:`
Fixed up and applied to the testing branch of iio.git on the
perhaps foolish basis "it's obviously correct" :)

> 
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> >   
>