From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: Giorgi Tchankvetadze <giorgitchankvetadze1997@gmail.com>,
antoniu.miclaus@analog.com, lars@metafoo.de,
Michael.Hennerich@analog.com, dlechner@baylibre.com,
nuno.sa@analog.com, andy@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: adc: ade9000: fix wrong macro names in ADE9000_ST_ERROR
Date: Sat, 28 Feb 2026 12:08:08 +0000 [thread overview]
Message-ID: <20260228120808.64f8299b@jic23-huawei> (raw)
In-Reply-To: <aaGt38ePGhonQRmd@ashevche-desk.local>
On Fri, 27 Feb 2026 16:44:47 +0200
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
> On Fri, Feb 27, 2026 at 02:52:45PM +0400, Giorgi Tchankvetadze wrote:
> > On Fri, Feb 27, 2026 at 2:33 PM Andy Shevchenko
> > <andriy.shevchenko@intel.com> wrote:
> >
> > > What about the current code that uses it? Is it even in use currently?
> > >Please, elaborate more in the commit message that we clearly understand
> > >that you spent time and investigated code and/or datasheet before crafting
> > >this change.
> >
> > Hi Andy. Thanks for the feedback !
> > The macro is currently unused in the driver, so this does not cause
> > a build failure.
>
> Drop it then?
Agreed. I'm generally in favour of complete definitions of the fields in
a register if any of them are used. However, in this case it's a define
of a mask covering multiple fields that we have no use for.
So drop it for now. It can come back in a patch that uses it.
Thanks,
Jonathan
>
> > Reference: ADE9000 datasheet (Rev. B, Page 61), STATUS1 register (0x403),
> > bits 28-31 define ERROR0 through ERROR3 status flags.
>
> Yes, good, this should be in the commit message.
>
next prev parent reply other threads:[~2026-02-28 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 10:09 [PATCH] iio: adc: ade9000: fix wrong macro names in ADE9000_ST_ERROR Giorgi Tchankvetadze
2026-02-27 10:33 ` Andy Shevchenko
2026-02-27 10:52 ` Giorgi Tchankvetadze
2026-02-27 14:44 ` Andy Shevchenko
2026-02-28 12:08 ` Jonathan Cameron [this message]
2026-03-02 5:57 ` Giorgi Tchankvetadze
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=20260228120808.64f8299b@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=dlechner@baylibre.com \
--cc=giorgitchankvetadze1997@gmail.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