From: Luis Chamberlain <mcgrof@kernel.org>
To: Mirsad Todorovac <mirsad.todorovac@alu.unizg.hr>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.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 v1 1/1] test_firmware: prevent race conditions by a correct implementation of locking
Date: Mon, 31 Jul 2023 10:27:30 -0700 [thread overview]
Message-ID: <ZMfvAhOfSP5UXN6l@bombadil.infradead.org> (raw)
In-Reply-To: <20230731165018.8233-1-mirsad.todorovac@alu.unizg.hr>
On Mon, Jul 31, 2023 at 06:50:19PM +0200, Mirsad Todorovac wrote:
> NOTE: This patch is tested against 5.4 stable
>
> NOTE: This is a patch for the 5.4 stable branch, not for the torvalds tree.
>
> The torvalds tree, and stable tree 5.10, 5.15, 6.1 and 6.4 branches
> were fixed in the separate
> commit ID 4acfe3dfde68 ("test_firmware: prevent race conditions by a correct implementation of locking")
> which was incompatible with 5.4
>
The above part is not part of the original commit, you also forgot to
mention the upstream commit:
[ Upstream commit 4acfe3dfde685a5a9eaec5555351918e2d7266a1 ]
> Fixes: c92316bf8e948 ("test_firmware: add batched firmware tests")
> Cc: Luis R. Rodriguez <mcgrof@kernel.org>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Russ Weight <russell.h.weight@intel.com>
> Cc: Takashi Iwai <tiwai@suse.de>
> Cc: Tianfei Zhang <tianfei.zhang@intel.com>
> Cc: Shuah Khan <shuah@kernel.org>
> Cc: Colin Ian King <colin.i.king@gmail.com>
> Cc: Randy Dunlap <rdunlap@infradead.org>
> Cc: linux-kselftest@vger.kernel.org
> Cc: stable@vger.kernel.org # v5.4
> Suggested-by: Dan Carpenter <error27@gmail.com>
Here you can add the above note in brackets:
[ explain your changes here from the original commit ]
Then, I see two commits upstream on Linus tree which are also fixes
but not merged on v5.4, did you want those applied too?
Luis
next prev parent reply other threads:[~2023-07-31 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 16:50 Mirsad Todorovac
2023-07-31 17:27 ` Luis Chamberlain [this message]
2023-08-01 8:24 ` Mirsad Todorovac
2023-08-01 9:57 ` Mirsad Todorovac
2023-08-04 6:45 ` 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=ZMfvAhOfSP5UXN6l@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=colin.i.king@gmail.com \
--cc=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.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
all inboxes | Powered by JetHome®