From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: JManeyrol@invensense.com, Jonathan.Cameron@huawei.com,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] iio: imu: inv_mpu6050: fix no data on MPU6050" failed to apply to 4.19-stable tree
Date: Mon, 11 Nov 2019 08:47:32 -0500 [thread overview]
Message-ID: <20191111134732.GB8496@sasha-vm> (raw)
In-Reply-To: <15734533311935@kroah.com>
On Mon, Nov 11, 2019 at 07:22:11AM +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 6e82ae6b8d11b948b74e71396efd8e074c415f44 Mon Sep 17 00:00:00 2001
>From: Jean-Baptiste Maneyrol <JManeyrol@invensense.com>
>Date: Wed, 16 Oct 2019 14:43:28 +0000
>Subject: [PATCH] iio: imu: inv_mpu6050: fix no data on MPU6050
>
>Some chips have a fifo overflow bit issue where the bit is always
>set. The result is that every data is dropped.
>
>Change fifo overflow management by checking fifo count against
>a maximum value.
>
>Add fifo size in chip hardware set of values.
>
>Fixes: f5057e7b2dba ("iio: imu: inv_mpu6050: better fifo overflow handling")
>Cc: stable@vger.kernel.org
>Signed-off-by: Jean-Baptiste Maneyrol <jmaneyrol@invensense.com>
>Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
I've resolved the conflict by also queueing up 22904bdff978 ("iio: imu:
mpu6050: Add support for the ICM 20602 IMU") on 4.19.
--
Thanks,
Sasha
prev parent reply other threads:[~2019-11-11 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 6:22 FAILED: patch "[PATCH] iio: imu: inv_mpu6050: fix no data on MPU6050" failed to apply to 4.19-stable tree gregkh
2019-11-11 13:47 ` Sasha Levin [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=20191111134732.GB8496@sasha-vm \
--to=sashal@kernel.org \
--cc=JManeyrol@invensense.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).