From: Dennis Dalessandro <dennis.dalessandro@intel•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Doug Ledford <dledford@redhat•com>,
Jason Gunthorpe <jgg@mellanox•com>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
"Michael J. Ruhl" <michael.j.ruhl@intel•com>,
Kaike Wan <kaike.wan@intel•com>
Subject: Re: linux-next: Fixes tag needs some work in the rdma tree
Date: Wed, 8 Jan 2020 08:05:58 -0500 [thread overview]
Message-ID: <67b5c37f-ff63-9ae5-fe80-0d2ac0821000@intel.com> (raw)
In-Reply-To: <20200108073349.2b270de3@canb.auug.org.au>
On 1/7/2020 3:33 PM, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 44ec5aa3c615 ("IB/hfi1: List all receive contexts from debugfs")
>
> Fixes tag
>
> Fixes: bf808b5039c ("IB/hfi1: Add kernel receive context info to debugfs")
>
> 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").
>
bf808b5039c
should be:
bf808b5039c6
A character got left off by mistake. Jason do you want to just fix this
in your tree directly? Do we let it go and just make sure to catch it
next time? Let me know if you want a new patch or something.
-Denny
next prev parent reply other threads:[~2020-01-08 13:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 20:33 linux-next: Fixes tag needs some work in the rdma tree Stephen Rothwell
2020-01-08 13:05 ` Dennis Dalessandro [this message]
2020-01-08 13:07 ` Jason Gunthorpe
-- strict thread matches above, loose matches on Subject: below --
2021-06-20 22:32 Stephen Rothwell
2021-04-21 22:13 Stephen Rothwell
2021-04-21 23:08 ` Jason Gunthorpe
2019-07-05 14:57 Stephen Rothwell
2019-07-05 15:01 ` Jason Gunthorpe
2019-07-05 15:19 ` Bodong Wang
2019-04-09 21:22 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=67b5c37f-ff63-9ae5-fe80-0d2ac0821000@intel.com \
--to=dennis.dalessandro@intel$(echo .)com \
--cc=dledford@redhat$(echo .)com \
--cc=jgg@mellanox$(echo .)com \
--cc=kaike.wan@intel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=michael.j.ruhl@intel$(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