From: Leon Romanovsky <leon@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Doug Ledford <dledford@redhat.com>,
Jason Gunthorpe <jgg@mellanox.com>,
Shiraz Saleem <shiraz.saleem@intel.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-fixes tree
Date: Mon, 17 Jul 2023 08:05:37 +0300 [thread overview]
Message-ID: <20230717050537.GA9461@unreal> (raw)
In-Reply-To: <20230717073649.5fc71a09@canb.auug.org.au>
On Mon, Jul 17, 2023 at 07:36:49AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> e77ac83ee5fd ("RDMA/irdma: Fix data race on CQP request done")
>
> Fixes tag
>
> Fixes: 915cc7ac0f8 ("RDMA/irdma: Add miscellaneous utility definitions")
>
> has these problem(s):
>
> - SHA1 should be at least 12 digits long
>
> In commit
>
> df56ce725d7c ("RDMA/irdma: Fix data race on CQP completion stats")
>
> Fixes tag
>
> Fixes: 915cc7ac0f8 ("RDMA/irdma: Add miscellaneous utility definitions")
>
> has these problem(s):
>
> - SHA1 should be at least 12 digits long
>
> In commit
>
> 13120f2d08fd ("RDMA/irdma: Add missing read barriers")
>
> Fixes tag
>
> Fixes: 3f49d684256 ("RDMA/irdma: Implement HW Admin Queue OPs")
>
> 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").
Thanks, fixed.
>
> --
> Cheers,
> Stephen Rothwell
prev parent reply other threads:[~2023-07-17 5:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 21:36 linux-next: Fixes tags need some work in the rdma-fixes tree Stephen Rothwell
2023-07-17 5:05 ` Leon Romanovsky [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=20230717050537.GA9461@unreal \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=jgg@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=shiraz.saleem@intel.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