From: Steve French <smfrench@gmail.com>
To: David Howells <dhowells@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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 16:43:42 -0600 [thread overview]
Message-ID: <CAH2r5mts6edG_a1bj7oxF5LdNU-qpor-xEoKFsf4L5-9fnNdTA@mail.gmail.com> (raw)
In-Reply-To: <1659485.1677187658@warthog.procyon.org.uk>
Fixed. And updated now in cifs-2.6.git for-next
On Thu, Feb 23, 2023 at 3:27 PM David Howells <dhowells@redhat.com> wrote:
>
> 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
>
--
Thanks,
Steve
next prev parent reply other threads:[~2023-02-23 22:44 UTC|newest]
Thread overview: 19+ 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
2023-02-23 22:43 ` Steve French [this message]
-- strict thread matches above, loose matches on Subject: below --
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=CAH2r5mts6edG_a1bj7oxF5LdNU-qpor-xEoKFsf4L5-9fnNdTA@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=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 \
/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).