From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
Networking <netdev@vger.kernel.org>
Cc: Johan Almbladh <johan.almbladh@anyfinetworks.com>,
David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tag needs some work in the bpf-next tree
Date: Fri, 8 Oct 2021 08:31:18 +1100 [thread overview]
Message-ID: <20211008083118.43f6d79f@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 372 bytes --]
Hi all,
In commit
065485ac5e86 ("mips, bpf: Fix Makefile that referenced a removed file")
Fixes tag
Fixes: 06b339fe5450 ("mips, bpf: Remove old BPF JIT implementations")
has these problem(s):
- Target SHA1 does not exist
Maybe you meant
Fixes: ebcbacfa50ec ("mips, bpf: Remove old BPF JIT implementations")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-10-07 21:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 21:31 Stephen Rothwell [this message]
2021-10-07 21:56 ` linux-next: Fixes tag needs some work in the bpf-next tree Daniel Borkmann
-- strict thread matches above, loose matches on Subject: below --
2022-08-24 5:00 Stephen Rothwell
2022-08-24 17:04 ` Kumar Kartikeya Dwivedi
2022-08-25 0:56 ` Alexei Starovoitov
2022-03-17 21:14 Stephen Rothwell
2020-08-01 11:00 Stephen Rothwell
2019-08-16 13:46 Stephen Rothwell
2019-08-16 14:35 ` Quentin Monnet
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=20211008083118.43f6d79f@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=johan.almbladh@anyfinetworks.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@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).