From: Jonathan LoBue <jlobue10@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: hdegoede@redhat.com, ilpo.jarvinen@linux.intel.com,
jic23@kernel.org, jagathjog1996@gmail.com, luke@ljones.dev,
benato.denis96@gmail.com, linux-iio@vger.kernel.org,
lkml@antheas.dev, derekjohn.clark@gmail.com
Subject: Re: [PATCH v1] iio: imu: bmi323: Add and enable ACPI Match Table
Date: Tue, 13 Feb 2024 09:14:50 -0800 [thread overview]
Message-ID: <4917806.31r3eYUQgx@nobara-ally-pc> (raw)
In-Reply-To: <CAHp75VeBqKiEWHyRjJt62VvrGKjG9S+kgMrbYEPBap311ZtZVw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1459 bytes --]
On Tuesday, February 13, 2024 2:49:24 AM PST Andy Shevchenko wrote:
> I'm lost. You sent a lot of patches / patch series all of which are v1. Can you:
> - use versioning (`git format-patch -v<X>...`, where <X> is a plain
> version number)
> - add a changelog here (after the cutter '---' line) to explain the
> history of the changes
> ?
Yes, I will do this. The changes so far included dropping the no longer
necessary DMI quirks portion in the bmc150 driver. I understand from
your comment that we want to add a comment in the bmc150 driver though
to explain what is going on with duplicate ACPI identifiers in different
drivers. I will add a similar comment in the bmi323 driver. The changes
so far also included the fixes that you requested earlier in bmi323:
dropping the duplicate header include entry (included already in other
header file), removing the unnecessary comma in the ACPI match table
portion, and removing the ACPI_PTR when invoking the ACPI match table.
> Since there is a collision please add a big comment in _both_ drivers
> before such ID to explain what's going on.
I will do this and add a changelog after the cutter as requested. Since there
are some changes from my initial submission attempt and with the additional
requested comments, is v2 going to be okay to use so there's no ambiguity
about which patch version to use? I will attach the version label with
git format-patch as requested. Thanks.
Best Regards,
Jon LoBue
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-02-13 17:14 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 16:05 [PATCH] iio: imu: bmi323: Support loading of bmi323 driver for ASUS ROG ALLY Jonathan LoBue
2024-02-10 15:25 ` Jonathan Cameron
2024-02-10 16:23 ` Jonathan LoBue
2024-02-10 16:49 ` Jonathan Cameron
2024-02-10 20:43 ` Jonathan LoBue
2024-02-10 22:32 ` [PATCH 1/2] iio: accel: bmc150: ASUS ROG ALLY Abort Loading Jonathan LoBue
2024-02-11 17:04 ` Andy Shevchenko
2024-02-12 7:21 ` Jonathan LoBue
2024-02-12 9:46 ` Andy Shevchenko
2024-02-13 2:39 ` [PATCH v1] iio: imu: bmi323: Add and enable ACPI Match Table Jonathan LoBue
2024-02-13 10:49 ` Andy Shevchenko
2024-02-13 17:14 ` Jonathan LoBue [this message]
2024-02-13 17:29 ` Andy Shevchenko
2024-02-13 22:38 ` [PATCH v2 1/2] iio: accel: bmc150: Duplicate ACPI entries Jonathan LoBue
2024-02-14 9:35 ` Andy Shevchenko
2024-02-14 15:07 ` Jonathan LoBue
2024-02-14 15:39 ` Andy Shevchenko
2024-02-14 16:16 ` Jonathan Cameron
2024-02-13 22:39 ` [PATCH v2 2/2] iio: imu: bmi323: Add and enable ACPI Match Table Jonathan LoBue
2024-02-14 9:39 ` Andy Shevchenko
2024-02-14 15:15 ` Jonathan LoBue
2024-02-14 15:31 ` Andy Shevchenko
2024-02-14 17:35 ` Jonathan LoBue
2024-02-14 18:21 ` Andy Shevchenko
2024-02-14 16:19 ` Jonathan Cameron
2024-02-13 2:47 ` [PATCH 1/2] iio: accel: bmc150: ASUS ROG ALLY Abort Loading Jonathan LoBue
2024-02-10 22:34 ` [PATCH 2/2] iio: imu: bmi323: Add and enable ACPI Match Table Jonathan LoBue
2024-02-11 16:31 ` Jonathan Cameron
2024-02-11 17:08 ` Andy Shevchenko
2024-02-12 7:30 ` Jonathan LoBue
2024-02-12 9:50 ` Andy Shevchenko
2024-02-12 17:33 ` 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=4917806.31r3eYUQgx@nobara-ally-pc \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox