From: David Howells <dhowells@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: dhowells@redhat.com,
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 fscache tree
Date: Tue, 02 Feb 2021 20:42:57 +0000 [thread overview]
Message-ID: <600007.1612298577@warthog.procyon.org.uk> (raw)
In-Reply-To: <20210203070915.06a1a574@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> In commit
>
> 51721d69bb95 ("afs: Fix error handling in afs_req_issue_op()")
>
> Fixes tag
>
> Fixes: 0dd1a43b5d74 ("afs: Fix error handling in afs_req_issue_op()")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> I have no idea which commit you meant :-(
Oops... I made the Fixes tag refer to the patch I was adding it to. Fixed
and repushed.
David
prev parent reply other threads:[~2021-02-02 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 20:09 linux-next: Fixes tag needs some work in the fscache tree Stephen Rothwell
2021-02-02 20:42 ` David Howells [this message]
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=600007.1612298577@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--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).