From: Lukas Wunner <lukas@wunner.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Sasha Levin <sashal@kernel.org>,
Nathan Chancellor <natechancellor@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.com>,
Mark Brown <broonie@kernel.org>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 4.19-stable 4/5] spi: bcm2835aux: Fix use-after-free on unbind
Date: Thu, 10 Dec 2020 08:01:42 +0100 [thread overview]
Message-ID: <20201210070142.GA20930@wunner.de> (raw)
In-Reply-To: <X9Ccm7X1id8Jj9SH@kroah.com>
On Wed, Dec 09, 2020 at 10:44:59AM +0100, Greg KH wrote:
> On Wed, Dec 09, 2020 at 10:38:18AM +0100, Lukas Wunner wrote:
> > On Wed, Dec 09, 2020 at 10:36:55AM +0100, Greg KH wrote:
> > > On Wed, Dec 09, 2020 at 09:37:47AM +0100, Lukas Wunner wrote:
> > > > Then please apply the series sans bcm2835aux patch and I'll follow up
> > > > with a two-patch series specifically for that driver.
> > >
> > > Can you just resend the whole series so we know we got it correct?
> >
> > The other patches in the series do not depend on the bcm2835aux patch,
> > so you can apply them independently.
>
> Ok, so I need to drop this patch from all of the other series you sent
> out? You can see how this is getting messy from my side :)
Is this workflow description still up-to-date?
http://kroah.com/log/blog/2019/08/14/patch-workflow-with-mutt-2019/
So you just select all patches in Mutt sans the bcm2835aux one
and apply them?
No I don't see how this is getting messy.
Thanks,
Lukas
next prev parent reply other threads:[~2020-12-10 7:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 12:31 [PATCH 4.19-stable 1/5] spi: Introduce device-managed SPI controller allocation Lukas Wunner
2020-12-06 12:31 ` [PATCH 4.19-stable 2/5] spi: bcm-qspi: Fix use-after-free on unbind Lukas Wunner
2020-12-06 12:31 ` [PATCH 4.19-stable 3/5] spi: bcm2835: " Lukas Wunner
2020-12-06 12:31 ` [PATCH 4.19-stable 4/5] spi: bcm2835aux: " Lukas Wunner
2020-12-08 0:49 ` Nathan Chancellor
2020-12-08 7:32 ` Lukas Wunner
2020-12-08 13:47 ` Sasha Levin
2020-12-08 17:11 ` Lukas Wunner
2020-12-08 20:28 ` Nathan Chancellor
2020-12-08 21:17 ` Sasha Levin
2020-12-09 8:37 ` Lukas Wunner
2020-12-09 9:36 ` Greg KH
2020-12-09 9:38 ` Lukas Wunner
2020-12-09 9:44 ` Greg KH
2020-12-10 7:01 ` Lukas Wunner [this message]
2020-12-10 12:45 ` Greg KH
2020-12-10 16:13 ` Lukas Wunner
2020-12-10 19:24 ` Lukas Wunner
2020-12-06 12:31 ` [PATCH 4.19-stable 5/5] spi: bcm2835: Release the DMA channel if probe fails after dma_init Lukas Wunner
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=20201210070142.GA20930@wunner.de \
--to=lukas@wunner.de \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.com \
--cc=gregkh@linuxfoundation.org \
--cc=natechancellor@gmail.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@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;
as well as URLs for NNTP newsgroup(s).