From: Dan Carpenter <dan.carpenter@linaro.org>
To: "Dr. David Alan Gilbert" <linux@treblig.org>
Cc: lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org,
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 19:28:02 +0300 [thread overview]
Message-ID: <c0bcb7b5-3155-445f-94ff-4020fe05109d@moroto.mountain> (raw)
In-Reply-To: <ZldRVBPi4utAfRd8@gallifrey>
On Wed, May 29, 2024 at 04:01:24PM +0000, Dr. David Alan Gilbert wrote:
> * Dan Carpenter (dan.carpenter@linaro.org) wrote:
> > On Wed, May 29, 2024 at 12:30:08AM +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>
> > > ---
> > > 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;
> > > -};
> > >
> >
> > Could you delete the blank line as well? Otherwise we have two blank
> > lines in a row and checkpatch will complain.
>
> Sure, v2 sent.
> (checkpatch didn't moan at me with or without).
Thanks. You'd need to apply the patch and re-run checkpatch.pl with the
-f option. It's not something that's obvious.
regards,
dan carpenter
prev parent reply other threads:[~2024-05-29 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 23:30 linux
2024-05-29 11:24 ` Nuno Sá
2024-05-29 14:34 ` Dan Carpenter
2024-05-29 16:01 ` Dr. David Alan Gilbert
2024-05-29 16:28 ` Dan Carpenter [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=c0bcb7b5-3155-445f-94ff-4020fe05109d@moroto.mountain \
--to=dan.carpenter@linaro.org \
--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
all inboxes | Powered by JetHome®