From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: stephan@gerhold.net, Jonathan.Cameron@huawei.com,
lorenzo@kernel.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] iio: imu: st_lsm6dsx: Fix selection of ST_LSM6DS3_ID" failed to apply to 4.19-stable tree
Date: Sun, 19 Jan 2020 10:32:53 -0500 [thread overview]
Message-ID: <20200119153253.GP1706@sasha-vm> (raw)
In-Reply-To: <1579440810243255@kroah.com>
On Sun, Jan 19, 2020 at 02:33:30PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.19-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From fb4fbc8904e786537e29329d791147389e1465a2 Mon Sep 17 00:00:00 2001
>From: Stephan Gerhold <stephan@gerhold.net>
>Date: Mon, 16 Dec 2019 13:41:20 +0100
>Subject: [PATCH] iio: imu: st_lsm6dsx: Fix selection of ST_LSM6DS3_ID
>
>At the moment, attempting to probe a device with ST_LSM6DS3_ID
>(e.g. using the st,lsm6ds3 compatible) fails with:
>
> st_lsm6dsx_i2c 1-006b: unsupported whoami [69]
>
>... even though 0x69 is the whoami listed for ST_LSM6DS3_ID.
>
>This happens because st_lsm6dsx_check_whoami() also attempts
>to match unspecified (zero-initialized) entries in the "id" array.
>ST_LSM6DS3_ID = 0 will therefore match any entry in
>st_lsm6dsx_sensor_settings (here: the first), because none of them
>actually have all 12 entries listed in the "id" array.
>
>Avoid this by additionally checking if "name" is set,
>which is only set for valid entries in the "id" array.
>
>Note: Although the problem was introduced earlier it did not surface until
>commit 52f4b1f19679 ("iio: imu: st_lsm6dsx: add support for accel/gyro unit of lsm9ds1")
>because ST_LSM6DS3_ID was the first entry in st_lsm6dsx_sensor_settings.
>
>Fixes: d068e4a0f921 ("iio: imu: st_lsm6dsx: add support to multiple devices with the same settings")
>Cc: <stable@vger.kernel.org> # 5.4
>Acked-by: Lorenzo Bianconi <lorenzo@kernel.org>
>Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
>Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
I don't think that this is needed on anything older than 5.4 because
they don't have 801a6e0af0c6 ("iio: imu: st_lsm6dsx: add support to
LSM6DSO"), the fixes tag might be misleading here a bit.
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-01-19 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 13:33 FAILED: patch "[PATCH] iio: imu: st_lsm6dsx: Fix selection of ST_LSM6DS3_ID" failed to apply to 4.19-stable tree gregkh
2020-01-19 15:32 ` Sasha Levin [this message]
2020-01-19 16:15 ` Stephan Gerhold
2020-01-19 18:55 ` Sasha Levin
2020-01-19 19:10 ` Stephan Gerhold
2020-01-19 19:28 ` Sasha Levin
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=20200119153253.GP1706@sasha-vm \
--to=sashal@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=lorenzo@kernel.org \
--cc=stable@vger.kernel.org \
--cc=stephan@gerhold.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