From: Trond Myklebust <trondmy@hammerspace.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: minoura makoto <minoura@valinux.co.jp>,
Hiroshi Shimamoto <h-shimamoto@nec.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
List Linux Next Mailing <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the nfs tree
Date: Thu, 15 Dec 2022 23:18:19 +0000 [thread overview]
Message-ID: <5ACA3AF2-C039-4BE8-9FA5-2BA5A7FF775A@hammerspace.com> (raw)
In-Reply-To: <20221215115449.71fa7b95@canb.auug.org.au>
> On Dec 14, 2022, at 19:54, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> In commit
>
> 405ab45b5afa ("SUNRPC: ensure the matching upcall is in-flight upon downcall")
>
> Fixes tag
>
> Fixes: Commit 9130b8dbc6ac ("SUNRPC: allow for upcalls for the same uid
>
> has these problem(s):
>
> - leading word 'Commit' unexpected
> - Subject has leading but no trailing parentheses
> - Subject has leading but no trailing quotes
> - Subject does not match target commit subject
> Just use
> git log -1 --format='Fixes: %h ("%s")'
>
> Please do not split Fixes tags over more than one line.
>
> --
> Cheers,
> Stephen Rothwell
Thanks Stephen! Sorry about missing that.
I’ve fixed up the offending line and pushed out a new linux-next branch.
_________________________________
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2022-12-15 23:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 0:54 linux-next: Fixes tag needs some work in the nfs tree Stephen Rothwell
2022-12-15 23:18 ` Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-04 7:36 Stephen Rothwell
2025-12-04 14:29 ` Trond Myklebust
2025-07-14 21:57 Stephen Rothwell
2025-07-14 22:30 ` Trond Myklebust
2025-07-14 21:54 Stephen Rothwell
2024-03-07 22:28 Stephen Rothwell
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=5ACA3AF2-C039-4BE8-9FA5-2BA5A7FF775A@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=h-shimamoto@nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=minoura@valinux.co.jp \
--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