Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Hans de Goede" <hdegoede@redhat.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.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: Sat, 14 Sep 2024 15:26:37 +0100	[thread overview]
Message-ID: <20240914152637.6972642f@jic23-huawei> (raw)
In-Reply-To: <ZuQGnqgdkJhyIiLK@smile.fi.intel.com>

On Fri, 13 Sep 2024 12:32:14 +0300
Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:

> On Thu, Sep 12, 2024 at 03:52:34PM +0200, Hans de Goede wrote:
> > Hi,
> > 
> > On 9/11/24 11:31 PM, Andy Shevchenko wrote:  
> > > The commit in question does not proove that ACPI ID exists.
> > > Quite likely it was a cargo cult addition while doint that
> > > for DT-based enumeration.  Drop most likely fake ACPI ID.
> > > 
> > > Googling for KMX61021L gives no useful results in regard to DSDT.
> > > Moreover, the official vendor ID in the registry for Kionix is KIOX.
> > > 
> > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>  
> > 
> > Thanks, patch looks good to me:  
> 
> Same Q here.
In meantime I've queued it up.  Can always drop it again
if it turns out we do have users.

Jonathan

> 
> >  Reviewed-by: Hans de Goede <hdegoede@redhat.com>  
> 
> And thank you for the reviews!
> 


      parent reply	other threads:[~2024-09-14 14:26 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
2024-09-14 14:26     ` 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=20240914152637.6972642f@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --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