From: John Hurley <john.hurley@netronome.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Miller <davem@davemloft.net>,
Networking <netdev@vger.kernel.org>,
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 net-next tree
Date: Tue, 23 Apr 2019 13:19:10 +0100 [thread overview]
Message-ID: <CAK+XE=k_qv4DDku8HBKRuqWKsze5z0W_pZuqa+jRaJKXZq8SOQ@mail.gmail.com> (raw)
In-Reply-To: <20190423072634.57cdf8b0@canb.auug.org.au>
On Mon, Apr 22, 2019 at 10:26 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> In commit
>
> 7d26c96052cd ("nfp: flower: fix size_t compile warning")
>
> Fixes tag
>
> Fixes: a6156a6ab0f9 ("nfp: flower: handle merge hint messages")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Did you mean
>
> Fixes: dbc2d68edc98 ("nfp: flower: handle merge hint messages")
>
Hi Stephen,
Yes, the fixes SHA1 tag you have is correct.
I have no idea how the incorrect one went in!
Thanks,
John
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2019-04-23 12:19 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 21:26 linux-next: Fixes tag needs some work in the net-next tree Stephen Rothwell
2019-04-23 12:19 ` John Hurley [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-26 21:37 Stephen Rothwell
2021-08-16 22:04 Stephen Rothwell
2021-08-17 7:53 ` Nikolay Aleksandrov
2021-04-18 21:53 Stephen Rothwell
2021-03-30 1:15 Stephen Rothwell
2021-03-26 23:03 Stephen Rothwell
2020-09-15 23:04 Stephen Rothwell
2020-06-01 23:12 Stephen Rothwell
2020-06-02 7:31 ` Ayush Sawal
2020-06-02 10:18 ` Stephen Rothwell
2020-06-02 10:30 ` Ayush Sawal
2020-04-22 22:16 Stephen Rothwell
2020-02-27 4:42 Stephen Rothwell
2020-02-27 9:01 ` Maxim Mikityanskiy
2020-02-17 4:23 Stephen Rothwell
2019-12-18 6:35 Stephen Rothwell
2019-11-04 21:01 Stephen Rothwell
2019-09-10 14:37 Stephen Rothwell
2019-08-01 22:54 Stephen Rothwell
2019-07-29 21:25 Stephen Rothwell
2019-07-22 21:35 Stephen Rothwell
[not found] ` <CANP3RGcqGrPnt9eOiAKRbxWVuBkRHRQdWPnANKwrYvtVnTqaSQ@mail.gmail.com>
2019-07-23 0:49 ` Stephen Rothwell
2019-07-03 21:42 Stephen Rothwell
2019-06-30 21:37 Stephen Rothwell
2019-04-05 5:58 Stephen Rothwell
2019-03-21 18:54 Stephen Rothwell
2019-02-25 8:00 Stephen Rothwell
2019-02-27 1:12 ` tanhuazhong
2019-02-27 2:23 ` Stephen Rothwell
2019-02-27 3:16 ` tanhuazhong
2019-02-19 22:31 Stephen Rothwell
2019-02-20 4:40 ` Vinod Koul
2019-02-20 5:38 ` Stephen Rothwell
2019-02-20 6:48 ` David Miller
2019-02-20 8:36 ` Jiri Pirko
2019-02-20 19:02 ` David Miller
2019-02-20 19:58 ` Jiri Pirko
2019-02-20 20:25 ` David Miller
2019-02-20 20:26 ` Jiri Pirko
2019-02-20 19:59 ` Stefano Brivio
2019-02-20 20:25 ` David Miller
2019-02-20 20:37 ` Stefano Brivio
2019-02-20 20:42 ` David Miller
2019-02-21 5:34 ` Vinod Koul
2019-02-11 22:17 Stephen Rothwell
2019-01-31 20:35 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='CAK+XE=k_qv4DDku8HBKRuqWKsze5z0W_pZuqa+jRaJKXZq8SOQ@mail.gmail.com' \
--to=john.hurley@netronome.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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).