From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mirsad Todorovac <mirsad.todorovac@alu.unizg.hr>
Cc: linux-kernel@vger.kernel.org,
"Luis R . Rodriguez" <mcgrof@kernel.org>,
Russ Weight <russell.h.weight@intel.com>,
Takashi Iwai <tiwai@suse.de>,
Tianfei Zhang <tianfei.zhang@intel.com>,
Shuah Khan <shuah@kernel.org>,
Colin Ian King <colin.i.king@gmail.com>,
Randy Dunlap <rdunlap@infradead.org>,
linux-kselftest@vger.kernel.org, stable@vger.kernel.org,
Dan Carpenter <error27@gmail.com>
Subject: Re: [PATCH v3 1/2] test_firmware: prevent race conditions by a correct implementation of locking
Date: Fri, 4 Aug 2023 13:22:31 +0200 [thread overview]
Message-ID: <2023080435-unweave-suspect-3299@gregkh> (raw)
In-Reply-To: <20230803165304.9200-1-mirsad.todorovac@alu.unizg.hr>
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
next prev parent reply other threads:[~2023-08-04 11:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 16:53 [PATCH v3 1/2] test_firmware: prevent race conditions by a correct implementation of locking Mirsad Todorovac
2023-08-04 11:22 ` Greg Kroah-Hartman [this message]
2023-08-04 17:15 ` [PATCH v3 1/2] [DONE REQ CHG] " Mirsad Todorovac
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=2023080435-unweave-suspect-3299@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=colin.i.king@gmail.com \
--cc=error27@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mirsad.todorovac@alu.unizg.hr \
--cc=rdunlap@infradead.org \
--cc=russell.h.weight@intel.com \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tianfei.zhang@intel.com \
--cc=tiwai@suse.de \
/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