public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Trond Myklebust <trondmy@gmail.com>
Cc: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>,
	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: Tue, 15 Jul 2025 07:54:41 +1000	[thread overview]
Message-ID: <20250715075441.10417fbd@canb.auug.org.au> (raw)

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

Hi all,

In commit

  9f9cfd0ebd6f ("pNFS/flexfiles: don't attempt pnfs on fatal DS errors")

Fixes tag

  Fixes: 260f32adb88 ("pNFS/flexfiles: Check the result of nfs4_pnfs_ds_connect")

has these problem(s):

  - SHA1 should be at least 12 digits long
    This can be fixed for the future 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").

Also, the Fixes tag line should be at the end of the commit message with
all the other commit message tags.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2025-07-14 21:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-14 21:54 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-12-04  7:36 linux-next: Fixes tag needs some work in the nfs tree Stephen Rothwell
2025-12-04 14:29 ` Trond Myklebust
2025-07-14 21:57 Stephen Rothwell
2025-07-14 22:30 ` Trond Myklebust
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
2021-01-10  2:14 Stephen Rothwell
2021-01-10 17:13 ` Trond Myklebust
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=20250715075441.10417fbd@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=tigran.mkrtchyan@desy.de \
    --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