From: Sasha Levin <sashal@kernel.org>
To: Sean Nyekjaer <sean@geanix.com>
Cc: linux-stable <stable@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rasmus Pedersen (RD SC)" <rap@serenergy.com>
Subject: Re: bcm2835aux: broken in (4.9), 4.14 and 4.19
Date: Fri, 6 Sep 2019 14:48:49 -0400 [thread overview]
Message-ID: <20190906184849.GC1528@sasha-vm> (raw)
In-Reply-To: <5f6bd329-3848-98aa-bae9-e988de0d361a@geanix.com>
On Thu, Sep 05, 2019 at 02:18:35PM +0200, Sean Nyekjaer wrote:
>Hi,
>
>Please consider picking:
>
>commit 7188a6f0eee3f1fae5d826cfc6d569657ff950ec
>Author: Martin Sperl <kernel@martin.sperl.org>
>Date: Sat Mar 30 09:30:58 2019 +0000
>
> spi: bcm2835aux: unifying code between polling and interrupt
>driven code
>
>commit c7de8500fd8ecbb544846dd5f11dca578c3777e1
>Author: Martin Sperl <kernel@martin.sperl.org>
>Date: Sat Mar 30 09:30:59 2019 +0000
>
> spi: bcm2835aux: remove dangerous uncontrolled read of fifo
>
>
>commit 73b114ee7db1750c0b535199fae383b109bd61d0
>Author: Martin Sperl <kernel@martin.sperl.org>
>Date: Sat Mar 30 09:31:00 2019 +0000
>
> spi: bcm2835aux: fix corruptions for longer spi transfers
>
>for stable kernel 4.14 and 4.19.
>
>If we want to fix this in 4.9 you should also pick:
>
>commit bc519d9574618e47a0c788000fb78da95e18d953
>Author: Rob Herring <robh@kernel.org>
>Date: Thu May 3 13:09:44 2018 -0500
>
> spi: bcm2835aux: ensure interrupts are enabled for shared handler
I've queued this as per your instructions (plus all 4 for 4.4), thank
you!
--
Thanks,
Sasha
prev parent reply other threads:[~2019-09-06 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 12:18 bcm2835aux: broken in (4.9), 4.14 and 4.19 Sean Nyekjaer
2019-09-06 18:48 ` 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=20190906184849.GC1528@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=rap@serenergy.com \
--cc=sean@geanix.com \
--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).