On Tue, Nov 24, 2020 at 07:28:44PM +0000, Sudip Mukherjee wrote:
On Tue, Nov 24, 2020 at 6:53 PM Sudip Mukherjee sudipm.mukherjee@gmail.com wrote:
On Tue, Nov 24, 2020 at 6:06 PM Greg KH gregkh@linuxfoundation.org wrote:
On Tue, Nov 24, 2020 at 01:41:23PM +0000, Sudip Mukherjee wrote:
On Mon, Nov 23, 2020 at 10:16:47AM +0100, gregkh@linuxfoundation.org wrote:
The patch below does not apply to the 5.4-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.
Here is the backport for all the stable tree from v4.9.y to v5.4.y.
I was modifying one of my script which pulls in the stablerc and stable-queue and I have completely messed up today :( Please drop this from v4.14.y. It will fail to build there. I had been working on the version for v4.14.y and v4.9.y, but I will keep it aside for today. Really sorry for the confusion.
v4.19.y also. :( I have rechecked and only v5.4.y is ok.
Sudip's patch for 4.19 is actually correct, but it depends on commit 5e844cc37a5c ("spi: Introduce device-managed SPI controller allocation"). If that commit is cherry-picked to 4.19 (applies cleanly), Sudip's patch compiles without errors.
I'm attaching Sudip's patch for re-application, barring any objections against applying 5e844cc37a5c to older stable kernels.
I had tried to make the patch dependency explicit by including the following tag in the commit message:
Cc: stable@vger.kernel.org # v4.9+: 123456789abc: spi: Introduce device-managed SPI controller allocation
I didn't know the SHA-1 hash the commit would get, so I used 123456789abc as a placeholder. (Both 5e844cc37a5c and the $subject patch were part of the same series.) Sorry for the confusion.
Thanks,
Lukas