From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jon Mason <jdmason@kudzu.us>,
NTB Mailing List <linux-ntb@googlegroups.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sanjay R Mehta <sanju.mehta@amd.com>,
Arindam Nath <arindam.nath@amd.com>,
Logan Gunthorpe <logang@deltatee.com>
Subject: linux-next: Fixes tag needs some work in the ntb tree
Date: Mon, 1 Jun 2020 17:44:50 +1000 [thread overview]
Message-ID: <20200601174450.7a0d79a3@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 831 bytes --]
Hi all,
In commit
eb3eabb28cf2 ("ntb_tool: pass correct struct device to dma_alloc_coherent")
Fixes tag
Fixes: 5648e56 ("NTB: ntb_perf: Add full multi-port NTB API support")
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").
In commit
55480afb82bd ("ntb_perf: pass correct struct device to dma_alloc_coherent")
Fixes tag
Fixes: 5648e56 ("NTB: ntb_perf: Add full multi-port NTB API support")
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").
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-06-01 7:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 7:44 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-20 20:58 linux-next: Fixes tag needs some work in the ntb tree Stephen Rothwell
2019-03-20 21:00 ` Logan Gunthorpe
2019-03-21 19:53 ` Jon Mason
2019-03-21 20:28 ` Stephen Rothwell
2019-03-22 15:34 ` Jon Mason
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=20200601174450.7a0d79a3@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arindam.nath@amd.com \
--cc=jdmason@kudzu.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-ntb@googlegroups.com \
--cc=logang@deltatee.com \
--cc=sanju.mehta@amd.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