From: Bodong Wang <bodong@mellanox.com>
To: Jason Gunthorpe <jgg@mellanox.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Doug Ledford <dledford@redhat.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Saeed Mahameed <saeedm@mellanox.com>
Subject: Re: linux-next: Fixes tag needs some work in the rdma tree
Date: Fri, 5 Jul 2019 15:19:26 +0000 [thread overview]
Message-ID: <ddbbbd7d-3c16-41cb-5df3-87eabb6516b5@mellanox.com> (raw)
In-Reply-To: <20190705150125.GE31525@mellanox.com>
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.
next prev parent reply other threads:[~2019-07-05 15:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 14:57 linux-next: Fixes tag needs some work in the rdma tree Stephen Rothwell
2019-07-05 15:01 ` Jason Gunthorpe
2019-07-05 15:19 ` Bodong Wang [this message]
-- 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
2020-01-07 20:33 Stephen Rothwell
2020-01-08 13:05 ` Dennis Dalessandro
2020-01-08 13:07 ` Jason Gunthorpe
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=ddbbbd7d-3c16-41cb-5df3-87eabb6516b5@mellanox.com \
--to=bodong@mellanox.com \
--cc=dledford@redhat.com \
--cc=jgg@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=saeedm@mellanox.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;
as well as URLs for NNTP newsgroup(s).