From: Trond Myklebust <trondmy@hammerspace.com>
To: "sfr@canb.auug.org.au" <sfr@canb.auug.org.au>
Cc: "smayhew@redhat.com" <smayhew@redhat.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the nfs tree
Date: Sun, 10 Jan 2021 17:13:39 +0000 [thread overview]
Message-ID: <2aa7f20d90445148c790d304379cdb55d95f4686.camel@hammerspace.com> (raw)
In-Reply-To: <20210110131423.0dedfd93@canb.auug.org.au>
Hi Stephen,
On Sun, 2021-01-10 at 13:14 +1100, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 2cc8aca9d547 ("NFS: Adjust fs_context error logging")
>
> Fixes tag
>
> Fixes: Fixes: ce8866f0913f ("NFS: Attach supplementary error
> information to fs_context.")
>
> has these problem(s):
>
> - No SHA1 recognised
>
> See duplicate "Fixes: " :-(
>
Sorry, that was my fault. I added the 'Fixes' tag when I applied the
patch. and failed to notice the copy-paste error.
I'll fix up the commit changelog.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2021-01-10 17:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 2:14 linux-next: Fixes tag needs some work in the nfs tree Stephen Rothwell
2021-01-10 17:13 ` Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-07 22:28 Stephen Rothwell
2022-12-15 0:54 Stephen Rothwell
2022-12-15 23:18 ` Trond Myklebust
2021-06-03 22:20 Stephen Rothwell
2020-12-14 10:38 Stephen Rothwell
2020-08-04 22:10 Stephen Rothwell
2020-05-14 22:33 Stephen Rothwell
2020-04-21 22:05 Stephen Rothwell
2020-04-03 21:55 Stephen Rothwell
2020-04-03 22:22 ` Trond Myklebust
2019-11-19 20:47 Stephen Rothwell
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=2aa7f20d90445148c790d304379cdb55d95f4686.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=smayhew@redhat.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).