linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jonathan Cameron <jic23@kernel.org>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	linux-iio@vger.kernel.org
Subject: Re: [PATCH v1] iio: proximity: sx9500: Fix typo in ACPI ID
Date: Wed, 01 Nov 2017 18:42:12 +0200	[thread overview]
Message-ID: <1509554532.10233.171.camel@linux.intel.com> (raw)
In-Reply-To: <20171101163001.12388-1-andriy.shevchenko@linux.intel.com>

On Wed, 2017-11-01 at 18:30 +0200, Andy Shevchenko wrote:
> It seems no one before even tried this device on Intel based
> platforms.
> I suddenly realized that there is a typo by a) looking into prototype
> hardware, and b) googling for both variants (current and proposed).
> 
> Thus, fix a typo in the driver to enable this sensor.

I think to be on the safest side we may just add a new ID.

> 
> Fixes: 4193c0f1d863 ("iio: driver for Semtech SX9500 proximity
> solution")
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
>  drivers/iio/proximity/sx9500.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/iio/proximity/sx9500.c
> b/drivers/iio/proximity/sx9500.c
> index 53c5d653e780..8f417ccacf22 100644
> --- a/drivers/iio/proximity/sx9500.c
> +++ b/drivers/iio/proximity/sx9500.c
> @@ -1021,7 +1021,7 @@ static const struct dev_pm_ops sx9500_pm_ops = {
>  };
>  
>  static const struct acpi_device_id sx9500_acpi_match[] = {
> -	{"SSX9500", 0},
> +	{"SASX9500", 0},
>  	{ },
>  };
>  MODULE_DEVICE_TABLE(acpi, sx9500_acpi_match);

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

      reply	other threads:[~2017-11-01 16:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-01 16:30 [PATCH v1] iio: proximity: sx9500: Fix typo in ACPI ID Andy Shevchenko
2017-11-01 16:42 ` Andy Shevchenko [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=1509554532.10233.171.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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;
as well as URLs for NNTP newsgroup(s).