linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Anna Schumaker <Anna.Schumaker@Netapp.com>,
	Trond Myklebust <trondmy@gmail.com>,
	NFS Mailing List <linux-nfs@vger.kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Chuck Lever <chuck.lever@oracle.com>,
	Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: linux-next: Fixes tag needs some work in the nfs-anna tree
Date: Wed, 16 Jan 2019 08:38:31 +1100	[thread overview]
Message-ID: <20190116083831.256824cf@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 438 bytes --]

[I am experimenting with checking the Fixes tags in commits in linux-next.
Please let me know if you think I am being too strict.]

Hi all,

Commit

  deaa5c96c2f7 ("SUNRPC: Address Kerberos performance/behavior regression")

has problem with this Fixes tag:

  Fixes: 918f3c1fe83c ("SUNRPC: Improve latency for interactive ... ")

The subject should match the subject of the fixed commit.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2019-01-15 21:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-15 21:38 Stephen Rothwell [this message]
2019-01-15 21:41 ` linux-next: Fixes tag needs some work in the nfs-anna tree Chuck Lever
2019-01-15 22:12   ` Takashi Iwai
2019-01-15 23:38     ` Paul Gortmaker
2019-01-16  6:32       ` Takashi Iwai
2019-01-16 15:24       ` Chuck Lever
2019-05-30 21:58 Stephen Rothwell
2019-10-21 20:48 Stephen Rothwell
2020-05-19 18:30 Stephen Rothwell
2020-06-26 23:01 Stephen Rothwell
2022-02-06 20:56 Stephen Rothwell
2022-10-03 21:21 Stephen Rothwell
2023-09-12 22:05 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=20190116083831.256824cf@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=Anna.Schumaker@Netapp.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --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).