All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan LoBue <jlobue10@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org,
	"Andy Shevchenko" <andy.shevchenko@gmail.com>,
	"Hans De Goede" <hdegoede@redhat.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"jagath jogj" <jagathjog1996@gmail.com>,
	"Luke Jones" <luke@ljones.dev>,
	"Denis Benato" <benato.denis96@gmail.com>,
	"Antheas Kapenekakis" <lkml@antheas.dev>,
	"Derek John Clark" <derekjohn.clark@gmail.com>
Subject: [PATCH v6 0/2] Add bmi323 support for ASUS ROG ALLY
Date: Fri, 16 Feb 2024 10:16:25 -0800	[thread overview]
Message-ID: <CAF6rpDwZaCJOpLEYayVW8_aXQwKdpcLCDSRjbTNk1rr43EPriQ@mail.gmail.com> (raw)

From: Jonathan LoBue <jlobue10@gmail.com>

This patch series adds comments about a duplicate ACPI identifier
between devices using bmc150 and bmi323. This series also adds the ACPI
match table for devices using bmi323 to allow those devices to load the
proper driver.

Changes since v5:
- Updated patch titles
- Add patch description to cover letter

Jonathan LoBue (2):
  iio: accel: bmc150: Document duplicate ACPI entries with bmi323 driver
  iio: imu: bmi323: Add ACPI Match Table

 drivers/iio/accel/bmc150-accel-i2c.c | 13 +++++++++++++
 drivers/iio/imu/bmi323/bmi323_i2c.c  | 20 ++++++++++++++++++++
 2 files changed, 33 insertions(+)
--
2.43.0

             reply	other threads:[~2024-02-16 18:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-16 18:16 Jonathan LoBue [this message]
2024-02-16 18:22 ` [PATCH v6 1/2] iio: accel: bmc150: Document duplicate ACPI entries with bmi323 driver Jonathan LoBue
2024-02-16 18:23 ` [PATCH v6 2/2] iio: imu: bmi323: Add ACPI Match Table Jonathan LoBue
2024-02-16 18:45 ` [PATCH v6 0/2] Add bmi323 support for ASUS ROG ALLY Hans de Goede
2024-02-17 17:22   ` Jonathan Cameron
2024-02-17 17:28     ` Jonathan LoBue

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=CAF6rpDwZaCJOpLEYayVW8_aXQwKdpcLCDSRjbTNk1rr43EPriQ@mail.gmail.com \
    --to=jlobue10@gmail.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=benato.denis96@gmail.com \
    --cc=derekjohn.clark@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jagathjog1996@gmail.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=lkml@antheas.dev \
    --cc=luke@ljones.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.