From: Jonathan Cameron <jic23@kernel.org>
To: J Lo <jlobue10@gmail.com>
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: Re: [PATCH v5 0/2] Add bmi323 support for ASUS ROG ALLY
Date: Fri, 16 Feb 2024 11:35:45 +0000 [thread overview]
Message-ID: <20240216113545.33b46e19@jic23-huawei> (raw)
In-Reply-To: <CAF6rpDwtj-mtpfFntf8XtTnF2vQMw4rtg1eV-kFGYj6r9hWvKA@mail.gmail.com>
On Thu, 15 Feb 2024 10:19:52 -0800
J Lo <jlobue10@gmail.com> wrote:
> From: Jonathan LoBue <jlobue10@gmail.com>
Hi Jonathan
Cover letter should always include at least a short overview of what
the patch is doing.
Long term this solution may be a pain to maintain.
The reasoning is the DT path where we have moved over time to allow
for fallback compatibles (same concept exists in ACPI even if it is
little used) to be used even if we don't recognise a ID read from
the chip. The intent being to allow old kernels to work with new
devices where they really are backwards compatible.
If that gets fixed in these drivers, we will have to explicitly
exclude ACPI IDs.
Hopefully we'll pick up such issues in review though so this should be fine.
I'd like input from Hans though on whether this solution of duplicating
the IDs generally works out longer term and is appropriate here.
Jonathan
>
> Changes since v4:
> - Fixed comment location in bmc150.
> - Fixed signed off by portion.
>
> Jonathan LoBue (2):
> iio: accel: bmc150: Duplicate ACPI entries
> iio: imu: bmi323: Add and enable 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
next prev parent reply other threads:[~2024-02-16 11:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 18:19 [PATCH v5 0/2] Add bmi323 support for ASUS ROG ALLY J Lo
2024-02-15 18:24 ` [PATCH v5 1/2] iio: accel: bmc150: Duplicate ACPI entries Jonathan LoBue
2024-02-16 11:37 ` Jonathan Cameron
2024-02-16 14:30 ` Jonathan LoBue
2024-02-16 15:49 ` Jonathan Cameron
2024-02-15 18:24 ` [PATCH v5 2/2] iio: imu: bmi323: Add and enable ACPI Match Table Jonathan LoBue
2024-02-16 11:41 ` Jonathan Cameron
2024-02-16 11:35 ` Jonathan Cameron [this message]
2024-02-16 12:01 ` [PATCH v5 0/2] Add bmi323 support for ASUS ROG ALLY Hans de Goede
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=20240216113545.33b46e19@jic23-huawei \
--to=jic23@kernel.org \
--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=jlobue10@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox