From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: m.othacehe@gmail.com, Jonathan.Cameron@huawei.com,
Stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] iio: vcnl4000: Fix i2c swapped word reading." failed to apply to 4.14-stable tree
Date: Mon, 8 Jun 2020 16:41:14 -0400 [thread overview]
Message-ID: <20200608204114.GS1407771@sasha-vm> (raw)
In-Reply-To: <1591619056246224@kroah.com>
On Mon, Jun 08, 2020 at 02:24:16PM +0200, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.14-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 18dfb5326370991c81a6d1ed6d1aeee055cb8c05 Mon Sep 17 00:00:00 2001
>From: Mathieu Othacehe <m.othacehe@gmail.com>
>Date: Sun, 3 May 2020 11:29:55 +0200
>Subject: [PATCH] iio: vcnl4000: Fix i2c swapped word reading.
>
>The bytes returned by the i2c reading need to be swapped
>unconditionally. Otherwise, on be16 platforms, an incorrect value will be
>returned.
>
>Taking the slow path via next merge window as its been around a while
>and we have a patch set dependent on this which would be held up.
>
>Fixes: 62a1efb9f868 ("iio: add vcnl4000 combined ALS and proximity sensor")
>Signed-off-by: Mathieu Othacehe <m.othacehe@gmail.com>
>Cc: <Stable@vger.kernel.org>
>Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
There were some context conflicts due to renaming of the lock (and it
not existing on 4.4). I've fixed it and queued for 4.14-4.4.
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-06-08 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 12:24 FAILED: patch "[PATCH] iio: vcnl4000: Fix i2c swapped word reading." failed to apply to 4.14-stable tree gregkh
2020-06-08 20:41 ` Sasha Levin [this message]
2020-06-09 6:10 ` Greg KH
2020-06-09 12:06 ` 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=20200608204114.GS1407771@sasha-vm \
--to=sashal@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=Stable@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=m.othacehe@gmail.com \
/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