From: Logan Gunthorpe <logang@deltatee.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
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>
Subject: Re: linux-next: Fixes tag needs some work in the ntb tree
Date: Wed, 20 Mar 2019 15:00:37 -0600 [thread overview]
Message-ID: <8a8ce003-c151-d04b-3ac9-8823a6c8ff7b@deltatee.com> (raw)
In-Reply-To: <20190321075818.24f9703a@canb.auug.org.au>
On 2019-03-20 2:58 p.m., Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> f4d0dd1064b8 ("NTB: ntb_transport: Ensure qp->tx_mw_dma_addr is initaliazed")
>
> Fixes tag
>
> Fixes: c27ccb899219 ("NTB: ntb_transport: Ensure the destination buffer is mapped for TX DMA")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Did you mean:
>
> c59666bb32b9 ("NTB: ntb_transport: Ensure the destination buffer is mapped for TX DMA")
My fault. I sent the fix patch with the fixes tag before the original
patch was merged upstream expecting them to be squashed. c59666bb32b9 is
the correct hash in upstream now.
Logan
next prev parent reply other threads:[~2019-03-20 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2019-03-21 19:53 ` Jon Mason
2019-03-21 20:28 ` Stephen Rothwell
2019-03-22 15:34 ` Jon Mason
-- strict thread matches above, loose matches on Subject: below --
2020-06-01 7:44 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=8a8ce003-c151-d04b-3ac9-8823a6c8ff7b@deltatee.com \
--to=logang@deltatee.com \
--cc=jdmason@kudzu.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-ntb@googlegroups.com \
--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