Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
	"Michael Hennerich" <Michael.Hennerich@analog.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: amplifiers: ad8366: make ad8366_info const
Date: Sun, 29 Jun 2025 18:03:39 +0100	[thread overview]
Message-ID: <20250629180339.760c189f@jic23-huawei> (raw)
In-Reply-To: <871eafac-f643-410b-b201-681551075a2c@baylibre.com>

On Sat, 28 Jun 2025 12:05:03 -0500
David Lechner <dlechner@baylibre.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@baylibre.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(-)
> >   
> 


      reply	other threads:[~2025-06-29 17:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-28 17:01 [PATCH] iio: accel: adxl345: make ad8366_info const David Lechner
2025-06-28 17:05 ` [PATCH] iio: amplifiers: ad8366: " David Lechner
2025-06-29 17:03   ` Jonathan Cameron [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=20250629180339.760c189f@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    /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