From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Trond Myklebust <trondmy@gmail.com>
Cc: Dan Aloni <dan@kernelim.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tag needs some work in the nfs tree
Date: Mon, 14 Dec 2020 21:38:13 +1100 [thread overview]
Message-ID: <20201214213813.0949d61c@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 593 bytes --]
Hi all,
In commit
526a842bec1d ("sunrpc: fix xs_read_xdr_buf for partial pages receive")
Fixes tag
Fixes: 277e4ab7d53 ("SUNRPC: Simplify TCP receive code by switching to
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
or later) just making sure it is not set (or set to "auto").
- Subject has leading but no trailing parentheses
- Subject has leading but no trailing quotes
Please do not split Fixes tags over more than one line.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-12-14 10:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 10:38 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-07 22:28 linux-next: Fixes tag needs some work in the nfs tree Stephen Rothwell
2022-12-15 0:54 Stephen Rothwell
2022-12-15 23:18 ` Trond Myklebust
2021-06-03 22:20 Stephen Rothwell
2021-01-10 2:14 Stephen Rothwell
2021-01-10 17:13 ` Trond Myklebust
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=20201214213813.0949d61c@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dan@kernelim.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=trondmy@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;
as well as URLs for NNTP newsgroup(s).