mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 v2] iio: adc: ade9000: remove unused ADE9000_ST_ERROR macro
Date: Mon, 2 Mar 2026 20:04:11 +0000	[thread overview]
Message-ID: <20260302200411.6ae331c7@jic23-huawei> (raw)
In-Reply-To: <aaVBMRU9wd6s4Nu0@ashevche-desk.local>

On Mon, 2 Mar 2026 09:50:09 +0200
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:

> On Mon, Mar 02, 2026 at 09:50:36AM +0400, Giorgi Tchankvetadze wrote:
> > The ADE9000_ST_ERROR macro references ADE9000_ST1_ERROR0
> > through ADE9000_ST1_ERROR3, but the actual defined symbols
> > use the BIT suffix. Since this macro is currently unused
> > in the driver, remove it entirely rather than fixing the names.
> > It can be reintroduced in a future patch when it is actually needed.
> > 
> > The individual error bit definitions (bits 28-31 of the STATUS1
> > register at 0x403) are retained as they follow the convention of
> > defining all register fields.
> > 
> > Reference: ADE9000 datasheet (Rev. B, Page 61), STATUS1 register
> > (0x403), bits 28-31 define ERROR0 through ERROR3 status flags.  
> 
> > v2:
> >  - Drop the unused macro entirely instead of fixing the references,
> >    as suggested by Andy Shevchenko and Jonathan Cameron.  
> 
> Suggested-by: Andy Shevchenko <andriy.shevchenko@intel.com>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
> 

Applied

Thanks,

J

      reply	other threads:[~2026-03-02 20:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02  5:50 Giorgi Tchankvetadze
2026-03-02  7:50 ` Andy Shevchenko
2026-03-02 20:04   ` 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=20260302200411.6ae331c7@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

all inboxes | Powered by JetHome®