From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"Jonathan Cameron" <jic23@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: [PATCH v1 1/1] iio: imu: kmx61: Drop most likely fake ACPI ID
Date: Mon, 16 Sep 2024 13:02:27 +0300 [thread overview]
Message-ID: <ZugCM56HrIgWu4PM@smile.fi.intel.com> (raw)
In-Reply-To: <aac0e587-3770-43c5-a9b1-4da4890c979a@redhat.com>
On Sat, Sep 14, 2024 at 03:47:21PM +0200, Hans de Goede wrote:
> On 9/13/24 11:32 AM, Andy Shevchenko wrote:
> > On Thu, Sep 12, 2024 at 03:52:34PM +0200, Hans de Goede wrote:
> >> On 9/11/24 11:31 PM, Andy Shevchenko wrote:
...
> > Same Q here.
>
> Yes I did look for KMX61021 in my DSDT collection and I did
> not find anything, neither does:
>
> https://www.catalog.update.microsoft.com/Search.aspx?q=kmx61021
>
> find anything.
Thanks for checking!
> So I believe that this one can really be dropped.
Good. I'm on the side here to drop and look for bug reports rather than
keeping and provoke using badly invented ACPI IDs (as we see already
in the example of ltr501).
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-09-16 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 21:31 [PATCH v1 1/1] iio: imu: kmx61: Drop most likely fake ACPI ID Andy Shevchenko
2024-09-12 13:52 ` Hans de Goede
2024-09-13 9:32 ` Andy Shevchenko
2024-09-14 13:47 ` Hans de Goede
2024-09-16 10:02 ` Andy Shevchenko [this message]
2024-09-14 14:26 ` Jonathan Cameron
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=ZugCM56HrIgWu4PM@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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