From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Steve French <smfrench@gmail.com>, CIFS <linux-cifs@vger.kernel.org>
Cc: Shyam Prasad N <sprasad@microsoft.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tag needs some work in the cifs tree
Date: Wed, 6 Jul 2022 08:06:15 +1000 [thread overview]
Message-ID: <20220706080615.11c5ede3@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 385 bytes --]
Hi all,
In commit
37c1ad516f2c ("cifs: fix race condition with delayed threads")
Fixes tag
Fixes: 37d488b3d38c ("cifs: change iface_list from array to sorted linked list")
has these problem(s):
- Target SHA1 does not exist
Maybe you meant
Fixes: aa45dadd34e4 ("cifs: change iface_list from array to sorted linked list")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-07-05 22:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 22:06 Stephen Rothwell [this message]
2022-07-06 5:37 ` [EXTERNAL] linux-next: Fixes tag needs some work in the cifs tree Shyam Prasad
2022-07-06 5:43 ` Steve French
-- strict thread matches above, loose matches on Subject: below --
2023-02-23 21:09 Stephen Rothwell
2023-02-23 21:27 ` David Howells
2023-02-23 22:43 ` Steve French
2022-11-15 20:41 Stephen Rothwell
2022-11-16 6:22 ` Steve French
2022-10-15 8:57 Stephen Rothwell
2022-10-15 15:06 ` Steve French
2022-10-05 23:30 Stephen Rothwell
2022-10-06 2:18 ` Steve French
2022-08-30 21:42 Stephen Rothwell
2022-08-30 22:10 ` Steve French
2022-08-24 6:37 Stephen Rothwell
2022-08-24 14:23 ` Steve French
2021-05-19 21:53 Stephen Rothwell
2021-05-20 0:21 ` Steve French
2019-05-24 4:27 Stephen Rothwell
2019-05-24 14:14 ` Steve French
2019-05-29 3:24 ` Murphy Zhou
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=20220706080615.11c5ede3@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=smfrench@gmail.com \
--cc=sprasad@microsoft.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).