From: Doug Ledford <dledford@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Jason Gunthorpe <jgg@mellanox.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Potnuri Bharat Teja <bharat@chelsio.com>
Subject: Re: linux-next: Fixes tag needs some work in the rdma-fixes tree
Date: Mon, 21 Oct 2019 10:50:33 -0400 [thread overview]
Message-ID: <c4377d50c8a30ae292cd7886909238ce4fb56ee5.camel@redhat.com> (raw)
In-Reply-To: <20191021184128.601ff09d@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
On Mon, 2019-10-21 at 18:41 +1100, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 612e0486ad08 ("iw_cxgb4: fix ECN check on the passive accept")
>
> Fixes tag
>
> Fixes: 92e7ae7172 ("iw_cxgb4: Choose appropriate hw mtu index and
> ISS for iWARP connections")
>
> has these problem(s):
>
> - SHA1 should be at least 12 digits long
> Can be fixed 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").
I'll leave it to Potnuri to fix his stuff. As for the rdma tree, the 10
digit hash is still unique as of today, so I won't rebase the official
branch to fix this. However, I'll see about adding a check for this in
my workflow. Thanks.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-10-21 14:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 7:41 linux-next: Fixes tag needs some work in the rdma-fixes tree Stephen Rothwell
2019-10-21 14:50 ` Doug Ledford [this message]
2019-10-21 15:15 ` Jason Gunthorpe
2019-10-21 15:39 ` Matteo Croce
2019-10-21 17:01 ` Jason Gunthorpe
2019-10-21 17:08 ` Matteo Croce
2019-10-21 17:11 ` Jason Gunthorpe
2019-10-21 17:25 ` Joe Perches
2019-10-21 17:39 ` Jason Gunthorpe
2019-10-21 19:32 ` Joe Perches
-- strict thread matches above, loose matches on Subject: below --
2024-02-05 22:03 Stephen Rothwell
2024-02-06 15:17 ` Jason Gunthorpe
2022-09-08 10:11 Stephen Rothwell
2019-04-22 20:57 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=c4377d50c8a30ae292cd7886909238ce4fb56ee5.camel@redhat.com \
--to=dledford@redhat.com \
--cc=bharat@chelsio.com \
--cc=jgg@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).