From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Leon Romanovsky <leon@kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: Fixes tag needs some work in the mlx5-next tree
Date: Tue, 2 Jul 2019 10:05:33 +1000 [thread overview]
Message-ID: <20190702100533.206ea0df@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 428 bytes --]
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")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-07-02 0:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 0:05 Stephen Rothwell [this message]
2019-07-02 4:09 ` linux-next: Fixes tag needs some work in the mlx5-next tree Leon Romanovsky
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=20190702100533.206ea0df@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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).