From: Shyam Prasad <Shyam.Prasad@microsoft.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Steve French <smfrench@gmail.com>,
CIFS <linux-cifs@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: RE: [EXTERNAL] linux-next: Fixes tag needs some work in the cifs tree
Date: Wed, 6 Jul 2022 05:37:17 +0000 [thread overview]
Message-ID: <TY2P153MB0238EBC99422B2008BA0916C94809@TY2P153MB0238.APCP153.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20220706080615.11c5ede3@canb.auug.org.au>
-----Original Message-----
From: Stephen Rothwell <sfr@canb.auug.org.au>
Sent: Wednesday, July 6, 2022 3:36 AM
To: Steve French <smfrench@gmail.com>; CIFS <linux-cifs@vger.kernel.org>
Cc: Shyam Prasad <Shyam.Prasad@microsoft.com>; Linux Kernel Mailing List <linux-kernel@vger.kernel.org>; Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: [EXTERNAL] linux-next: Fixes tag needs some work in the cifs tree
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
-------------------------------------
Good catch. I must have used a different branch.
Steve, can you please fix the SHA1 in your branch?
Regards,
Shyam
next prev parent reply other threads:[~2022-07-06 5:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 22:06 linux-next: Fixes tag needs some work in the cifs tree Stephen Rothwell
2022-07-06 5:37 ` Shyam Prasad [this message]
2022-07-06 5:43 ` [EXTERNAL] " Steve French
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=TY2P153MB0238EBC99422B2008BA0916C94809@TY2P153MB0238.APCP153.PROD.OUTLOOK.COM \
--to=shyam.prasad@microsoft.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=smfrench@gmail.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