[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5ACA3AF2-C039-4BE8-9FA5-2BA5A7FF775A@hammerspace.com>
Date: Thu, 15 Dec 2022 23:18:19 +0000
From: Trond Myklebust <trondmy@...merspace.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
CC: minoura makoto <minoura@...inux.co.jp>,
Hiroshi Shimamoto <h-shimamoto@....com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
List Linux Next Mailing <linux-next@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the nfs tree
> On Dec 14, 2022, at 19:54, Stephen Rothwell <sfr@...b.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@...merspace.com
Powered by blists - more mailing lists