From: Leon Romanovsky <leon@kernel•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Saeed Mahameed <saeedm@mellanox•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 mlx5-next tree
Date: Tue, 2 Jul 2019 07:09:24 +0300 [thread overview]
Message-ID: <20190702040924.GP4727@mtr-leonro.mtl.com> (raw)
In-Reply-To: <20190702100533.206ea0df@canb.auug.org.au>
On Tue, Jul 02, 2019 at 10:05:33AM +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")
Right, unfortunately this commit was already merged.
Thanks
>
> --
> Cheers,
> Stephen Rothwell
prev parent reply other threads:[~2019-07-02 4:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 0:05 linux-next: Fixes tag needs some work in the mlx5-next tree Stephen Rothwell
2019-07-02 4:09 ` Leon Romanovsky [this message]
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=20190702040924.GP4727@mtr-leonro.mtl.com \
--to=leon@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=saeedm@mellanox$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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