From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: Nikhil Gautam <nikhilgtr@gmail.com>,
linux-iio@vger.kernel.org, nuno.sa@analog.com, andy@kernel.org
Subject: Re: [PATCH] iio: chemical: bme680: remove unused BME680_NUM_CHANNELS macro
Date: Sun, 19 Apr 2026 18:50:41 +0100 [thread overview]
Message-ID: <20260419185041.705d2db2@jic23-huawei> (raw)
In-Reply-To: <710e2da4-2815-4137-84c4-1f148ec0a23f@baylibre.com>
On Tue, 7 Apr 2026 09:28:54 -0500
David Lechner <dlechner@baylibre.com> wrote:
> On 4/7/26 4:03 AM, Nikhil Gautam wrote:
> > The BME680_NUM_CHANNELS macro is not used anywhere in the driver.
> > Remove it to avoid keeping dead code and to improve readability.
> >
> > No functional change intended.
> >
> > Signed-off-by: Nikhil Gautam <nikhilgtr@gmail.com>
> > ---
> > drivers/iio/chemical/bme680.h | 1 -
> > 1 file changed, 1 deletion(-)
> >
> > diff --git a/drivers/iio/chemical/bme680.h b/drivers/iio/chemical/bme680.h
> > index 7d86ed8b02e6..e10d3aaaca23 100644
> > --- a/drivers/iio/chemical/bme680.h
> > +++ b/drivers/iio/chemical/bme680.h
> > @@ -68,7 +68,6 @@
> > /* Datasheet Section 1.1, Table 1 */
> > #define BME680_STARTUP_TIME_US 2000
> >
> > -#define BME680_NUM_CHANNELS 4
> > #define BME680_NUM_BULK_READ_REGS 15
> >
> > /* Calibration Parameters */
>
> It looks like it was intended to be used in drivers/iio/chemical/bme680_core.c:
Agreed. I think probably better to use it than remove it?
>
> struct bme680_data {
> struct regmap *regmap;
> struct bme680_calib bme680;
> struct mutex lock; /* Protect multiple serial R/W ops to device. */
> u8 oversampling_temp;
> u8 oversampling_press;
> u8 oversampling_humid;
> u8 preheat_curr_mA;
> u16 heater_dur;
> u16 heater_temp;
>
> struct {
> s32 chan[4];
> aligned_s64 ts;
> } scan;
>
prev parent reply other threads:[~2026-04-19 17:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 9:03 [PATCH] iio: chemical: bme680: remove unused BME680_NUM_CHANNELS macro Nikhil Gautam
2026-04-07 14:28 ` David Lechner
2026-04-19 17:50 ` 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=20260419185041.705d2db2@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=nikhilgtr@gmail.com \
--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