From: "Nuno Sá" <noname.nuno@gmail.com>
To: linux@treblig.org, lars@metafoo.de, Michael.Hennerich@analog.com,
jic23@kernel.org
Cc: linux-iio@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: iio: adt7316: remove unused struct 'adt7316_limit_regs'
Date: Wed, 29 May 2024 13:24:59 +0200 [thread overview]
Message-ID: <23d5359dca83dd803655b0990479f6fb0eadc61c.camel@gmail.com> (raw)
In-Reply-To: <20240528233008.191403-1-linux@treblig.org>
On Wed, 2024-05-29 at 00:30 +0100, linux@treblig.org wrote:
> From: "Dr. David Alan Gilbert" <linux@treblig.org>
>
> 'adt7316_limit_regs' has never been used since the original
> commit 35f6b6b86ede ("staging: iio: new ADT7316/7/8 and ADT7516/7/9
> driver").
>
> The comment above it is a copy-and-paste from a different struct.
>
> Remove both the struct and the comment.
>
> Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
> ---
Reviewed-by: Nuno Sa <nuno.sa@analog.com>
> drivers/staging/iio/addac/adt7316.c | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/drivers/staging/iio/addac/adt7316.c
> b/drivers/staging/iio/addac/adt7316.c
> index 79467f056a05..23d036d2802c 100644
> --- a/drivers/staging/iio/addac/adt7316.c
> +++ b/drivers/staging/iio/addac/adt7316.c
> @@ -209,14 +209,6 @@ struct adt7316_chip_info {
> #define ADT7316_TEMP_AIN_INT_MASK \
> (ADT7316_TEMP_INT_MASK)
>
> -/*
> - * struct adt7316_chip_info - chip specific information
> - */
> -
> -struct adt7316_limit_regs {
> - u16 data_high;
> - u16 data_low;
> -};
>
> static ssize_t adt7316_show_enabled(struct device *dev,
> struct device_attribute *attr,
next prev parent reply other threads:[~2024-05-29 11:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 23:30 [PATCH] staging: iio: adt7316: remove unused struct 'adt7316_limit_regs' linux
2024-05-29 11:24 ` Nuno Sá [this message]
2024-05-29 14:34 ` Dan Carpenter
2024-05-29 16:01 ` Dr. David Alan Gilbert
2024-05-29 16:28 ` Dan Carpenter
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=23d5359dca83dd803655b0990479f6fb0eadc61c.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux@treblig.org \
/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