[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ddbbbd7d-3c16-41cb-5df3-87eabb6516b5@mellanox.com>
Date: Fri, 5 Jul 2019 15:19:26 +0000
From: Bodong Wang <bodong@...lanox.com>
To: Jason Gunthorpe <jgg@...lanox.com>,
Stephen Rothwell <sfr@...b.auug.org.au>
CC: Doug Ledford <dledford@...hat.com>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Saeed Mahameed <saeedm@...lanox.com>
Subject: Re: linux-next: Fixes tag needs some work in the rdma tree
On 7/5/2019 10:01 AM, Jason Gunthorpe wrote:
> On Sat, Jul 06, 2019 at 12:57:05AM +1000, Stephen Rothwell wrote:
>> Hi all,
>>
>> In commit
>>
>> 16fff98a7e82 ("net/mlx5: E-Switch, Reg/unreg function changed event at correct stage")
>>
>> Fixes tag
>>
>> Fixes: 61fc880839e6 ("net/mlx5: E-Switch, Handle representors creation in handler context")
>>
>> has these problem(s):
>>
>> - Target SHA1 does not exist
>>
>> Did you mean
>>
>> Fixes: ac35dcd6e4bd ("net/mlx5: E-Switch, Handle representors creation in handler context")
> You are correct, unfortunately the trees can't be rebased at this
> point to fix it.
>
> Thanks,
> Jason
I think I fetched the tag when original patch was not merged yet. Need
to figure out a way to detect such miss match.
Powered by blists - more mailing lists