From: Jason Gunthorpe <jgg@nvidia•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Doug Ledford <dledford@redhat•com>,
Bob Pearson <rpearsonhpe@gmail•com>,
Selvin Xavier <selvin.xavier@broadcom•com>,
Devesh Sharma <devesh.sharma@broadcom•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: Fixes tags need some work in the rdma tree
Date: Mon, 2 Nov 2020 19:45:39 -0400 [thread overview]
Message-ID: <20201102234539.GK2620339@nvidia.com> (raw)
In-Reply-To: <20201103083730.539fe81c@canb.auug.org.au>
On Tue, Nov 03, 2020 at 08:37:30AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 32fabd9b163b ("RDMA/rxe: Compute PSN windows correctly")
>
> Fixes tag
>
> Fixes: 8700e3e7c485 ("Soft RoCE (RXE) - The software RoCE driver")
>
> has these problem(s):
>
> - Subject does not match target commit subject
> Just use
> git log -1 --format='Fixes: %h ("%s")'
>
> Maybe you meant
>
> Fixes: 8700e3e7c485 ("Soft RoCE driver")
>
> In commit
>
> b67ffe884bdd ("RDMA/bnxt_re: Fix entry size during SRQ create")
>
> Fixes tag
>
> Fixes: 2bb3c32c5c5f ("RDMA/bnxt_re: Change wr posting logic to accommodate variable wqes")
>
> has these problem(s):
>
> - Subject does not match target commit subject
> Just use
> git log -1 --format='Fixes: %h ("%s")'
I don't usually like to rebase this tree, but I just pushed this, so
lets fix them.
My checker script noticed but I didn't notice the output in all the
other spam :\
I would be happy if the 0-day folks could run these checks too
Jason
prev parent reply other threads:[~2020-11-02 23:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 21:37 linux-next: Fixes tags need some work in the rdma tree Stephen Rothwell
2020-11-02 23:45 ` Jason Gunthorpe [this message]
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=20201102234539.GK2620339@nvidia.com \
--to=jgg@nvidia$(echo .)com \
--cc=devesh.sharma@broadcom$(echo .)com \
--cc=dledford@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rpearsonhpe@gmail$(echo .)com \
--cc=selvin.xavier@broadcom$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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