[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2023080435-unweave-suspect-3299@gregkh>
Date: Fri, 4 Aug 2023 13:22:31 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Mirsad Todorovac <mirsad.todorovac@....unizg.hr>
Cc: linux-kernel@...r.kernel.org,
"Luis R . Rodriguez" <mcgrof@...nel.org>,
Russ Weight <russell.h.weight@...el.com>,
Takashi Iwai <tiwai@...e.de>,
Tianfei Zhang <tianfei.zhang@...el.com>,
Shuah Khan <shuah@...nel.org>,
Colin Ian King <colin.i.king@...il.com>,
Randy Dunlap <rdunlap@...radead.org>,
linux-kselftest@...r.kernel.org, stable@...r.kernel.org,
Dan Carpenter <error27@...il.com>
Subject: Re: [PATCH v3 1/2] test_firmware: prevent race conditions by a
correct implementation of locking
On Thu, Aug 03, 2023 at 06:53:04PM +0200, Mirsad Todorovac wrote:
> [ Upstream commit 4acfe3dfde685a5a9eaec5555351918e2d7266a1 ]
<snip>
Ok, I am totally confused as to what patch is the newest one, and which
is for what branches, sorry.
So, I've deleted all of the patches from my review queue and I would ask
that you start over.
Note, if you put the kernel version in the subject line, it makes it
simpler for me to understand what goes where.
Here is an example to follow:
https://lore.kernel.org/r/20230802170227.1590187-1-eahariha@linux.microsoft.com
There are loads of other examples on the stable mailing list, please
don't make it hard for me to understand what to do here, make it obvious
as I'm dealing with hundreds of patches a day.
thanks,
greg k-h
Powered by blists - more mailing lists