Messages in this thread | | | From | Jon Mason <> | Date | Thu, 21 Mar 2019 15:53:47 -0400 | Subject | Re: linux-next: Fixes tag needs some work in the ntb tree |
| |
On Wed, Mar 20, 2019 at 5:00 PM Logan Gunthorpe <logang@deltatee.com> wrote: > > > > 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.
I've corrected the patch in my git branches and repushed.
Is there an existing set of tools/scripts I should run to prevent things like this from happening?
Thanks, Jon
> > Logan >
| |