From: David Howells <dhowells@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: dhowells@redhat.com, Steve French <smfrench@gmail.com>,
CIFS <linux-cifs@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the cifs tree
Date: Thu, 23 Feb 2023 21:27:38 +0000 [thread overview]
Message-ID: <1659485.1677187658@warthog.procyon.org.uk> (raw)
In-Reply-To: <20230224080931.6433105a@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> In commit
>
> d7830041d59a ("cifs: Add some missing xas_retry() calls")
>
> Fixes tag
>
> Fixes: 5f0955c98375 ("cifs: Add some helper functions")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: b8713c4dbfa3 ("cifs: Add some helper functions")
Sorry, yes, I was on my branch and not the one with Steve's applied version of
the patches.
David
next prev parent reply other threads:[~2023-02-23 21:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 21:09 linux-next: Fixes tag needs some work in the cifs tree Stephen Rothwell
2023-02-23 21:27 ` David Howells [this message]
2023-02-23 22:43 ` Steve French
-- strict thread matches above, loose matches on Subject: below --
2025-07-03 22:26 Stephen Rothwell
2025-07-03 23:47 ` Steve French
2025-07-04 6:43 ` Wang Zhaolong
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
2022-07-05 22:06 Stephen Rothwell
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=1659485.1677187658@warthog.procyon.org.uk \
--to=dhowells@redhat.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