public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: "Derek J. Clark" <derekjohn.clark@gmail.com>,
	David Lechner <dlechner@baylibre.com>,
	Andy Shevchenko <andy@kernel.org>,
	Alex Lanzano <lanzano.alex@gmail.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] iio: bmi270_i2c: Add MODULE_DEVICE_TABLE for BMI260/270
Date: Sun, 11 Jan 2026 13:03:46 +0000	[thread overview]
Message-ID: <20260111130346.73ecb12d@jic23-huawei> (raw)
In-Reply-To: <aV7KdXkQkI5XsoF3@smile.fi.intel.com>

On Wed, 7 Jan 2026 23:04:53 +0200
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:

> On Tue, Jan 06, 2026 at 05:45:19AM +0000, Derek J. Clark wrote:
> > Currently BMI260 & BMI270 devices do not automatically load this
> > driver. To fix this, add missing MODULE_DEVICE_TABLE for the i2c,
> > acpi, and of device tables so the driver will load when the hardware
> > is detected.
> > 
> > Tested on my OneXPlayer F1 Pro.  
> 
> No objections,
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
> 
Applied to the togreg branch of iio.git and pushed out as testing.

These are always a bit of a corner case wrt to whether we should treat
them as a fix.  It never worked though so I'm not going to rush them in.
If you want it applied to stable kernels, I'm fine with a request for
that after the next merge window.

Thanks,

Jonathan



      reply	other threads:[~2026-01-11 13:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06  5:45 [PATCH] iio: bmi270_i2c: Add MODULE_DEVICE_TABLE for BMI260/270 Derek J. Clark
2026-01-07 21:04 ` Andy Shevchenko
2026-01-11 13:03   ` 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=20260111130346.73ecb12d@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=derekjohn.clark@gmail.com \
    --cc=dlechner@baylibre.com \
    --cc=lanzano.alex@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.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