MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Date:   Thu, 11 Nov 2021 13:46:01 +0100
From:   Michael Walle <michael@walle.cc>
To:     Mark Brown <broonie@kernel.org>
Cc:     linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
        Andy Shevchenko <andy.shevchenko@gmail.com>,
        =?UTF-8?Q?Uwe_Kleine-K=C3=B6nig?= <u.kleine-koenig@pengutronix.de>,
        Lukas Wunner <lukas@wunner.de>, stable@vger.kernel.org
Subject: Re: [PATCH] spi: fix use-after-free of the add_lock mutex
In-Reply-To: <YY0Oe9NjhfUvq0J+@sirena.org.uk>
References: <20211111083713.3335171-1-michael@walle.cc>
 <YY0Oe9NjhfUvq0J+@sirena.org.uk>
User-Agent: Roundcube Webmail/1.4.11
Message-ID: <20cde88dd11fde7f6847506ffcaa67ed@walle.cc>
Precedence: bulk

Am 2021-11-11 13:37, schrieb Mark Brown:
> On Thu, Nov 11, 2021 at 09:37:13AM +0100, Michael Walle wrote:
> 
>> ---
>> changes since RFC:
>>  - fix call graph indendation in commit message
> 
> If you are sending a new version of something please flag that in the
> commit message, this helps both people and automated systems identify
> that this is a new version of the same thing.

Are RFC patches eligible to be picked up? I wasn't sure if I had to
resend it at all. But since there was a mistake in the commit message
anyway, I went ahead and the the first "real" version. How would
you flag that? Isn't changing the subject from "[PATCH RFC]" (ok it
was "RFC PATCH", my bad) to "[PATCH]" enough?

-michael