From: Jonathan Cameron <jic23@kernel.org>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"Nuno Sá" <nuno.sa@analog.com>
Subject: Re: [PATCH v2 1/2] iio: adc: ad4080: use lowercase device name
Date: Sat, 31 May 2025 18:07:53 +0100 [thread overview]
Message-ID: <20250531180753.12357ec5@jic23-huawei> (raw)
In-Reply-To: <20250526082228.4961-1-antoniu.miclaus@analog.com>
On Mon, 26 May 2025 11:22:27 +0300
Antoniu Miclaus <antoniu.miclaus@analog.com> wrote:
> Update the .name field in the ad4080_chip_info struct
> from "AD4080" to "ad4080" to follow the common convention
> in IIO drivers of using lowercase names for device identifiers.
>
> Fixes: 1ff3f56f846b ("iio: adc: ad4080: add driver support")
> Reviewed-by: Nuno Sá <nuno.sa@analog.com>
> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
I squashed both patches into the original commit as that is still
on a tree that I can rebase as I'll do that on rc1 anyway once available.
Thanks,
Jonathan
> ---
> changes in v2:
> - drop "no functional changes" from commit body
> - add fixes tag
> drivers/iio/adc/ad4080.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/adc/ad4080.c b/drivers/iio/adc/ad4080.c
> index e8b2e5e7a68a..c36eb41d738a 100644
> --- a/drivers/iio/adc/ad4080.c
> +++ b/drivers/iio/adc/ad4080.c
> @@ -433,7 +433,7 @@ static const struct iio_chan_spec ad4080_channel = {
> };
>
> static const struct ad4080_chip_info ad4080_chip_info = {
> - .name = "AD4080",
> + .name = "ad4080",
> .product_id = AD4080_CHIP_ID,
> .scale_table = ad4080_scale_table,
> .num_scales = ARRAY_SIZE(ad4080_scale_table),
prev parent reply other threads:[~2025-05-31 17:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 8:22 [PATCH v2 1/2] iio: adc: ad4080: use lowercase device name Antoniu Miclaus
2025-05-26 8:22 ` [PATCH v2 2/2] iio: adc: ad4080: extend check for data lanes num Antoniu Miclaus
2025-05-31 17:07 ` 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=20250531180753.12357ec5@jic23-huawei \
--to=jic23@kernel.org \
--cc=antoniu.miclaus@analog.com \
--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