From: Lukas Wunner <lukas@wunner.de>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Saravana Kannan <saravanak@google.com>,
Mark Brown <broonie@kernel.org>,
linux-spi@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 5.12 03/43] spi: Fix spi device unregister flow
Date: Sun, 6 Jun 2021 13:10:28 +0200 [thread overview]
Message-ID: <20210606111028.GA20948@wunner.de> (raw)
In-Reply-To: <20210603170734.3168284-3-sashal@kernel.org>
On Thu, Jun 03, 2021 at 01:06:53PM -0400, Sasha Levin wrote:
> From: Saravana Kannan <saravanak@google.com>
>
> [ Upstream commit c7299fea67696db5bd09d924d1f1080d894f92ef ]
This commit shouldn't be backported to stable by itself, it requires
that the following fixups are applied on top of it:
* Upstream commit 27e7db56cf3d ("spi: Don't have controller clean up spi
device before driver unbind")
* spi.git commit 2ec6f20b33eb ("spi: Cleanup on failure of initial setup")
https://git.kernel.org/broonie/spi/c/2ec6f20b33eb
Note that the latter is queued for v5.13, but hasn't landed there yet.
So you probably need to back out c7299fea6769 from the stable queue and
wait for 2ec6f20b33eb to land in upstream.
Since you've applied c7299fea6769 to v5.12, v5.10, v5.4, v4.14 and v4.19
stable trees, the two fixups listed above need to be backported to all
of them.
Thanks,
Lukas
next prev parent reply other threads:[~2021-06-06 11:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210603170734.3168284-1-sashal@kernel.org>
2021-06-03 17:06 ` [PATCH AUTOSEL 5.12 03/43] spi: Fix spi device unregister flow Sasha Levin
2021-06-06 11:10 ` Lukas Wunner [this message]
2021-06-10 17:55 ` Sasha Levin
2021-06-10 19:22 ` Saravana Kannan
2021-06-10 19:26 ` Lukas Wunner
2021-06-10 19:30 ` Saravana Kannan
2021-06-10 22:29 ` Lukas Wunner
2021-06-10 23:01 ` Saravana Kannan
2021-06-03 17:06 ` [PATCH AUTOSEL 5.12 04/43] spi: spi-zynq-qspi: Fix stack violation bug Sasha Levin
2021-06-03 17:07 ` [PATCH AUTOSEL 5.12 16/43] spi: sprd: Add missing MODULE_DEVICE_TABLE 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=20210606111028.GA20948@wunner.de \
--to=lukas@wunner.de \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=saravanak@google.com \
--cc=sashal@kernel.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).