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: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Jonathan Lemon <jonathan.lemon@gmail•com>
Subject: linux-next: Fixes tag needs some work in the bpf tree
Date: Tue, 11 Jun 2019 20:05:56 +1000 [thread overview]
Message-ID: <20190611200556.4a09514d@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 447 bytes --]
Hi all,
In commit
605465dd0c27 ("bpf: lpm_trie: check left child of last leftmost node for NULL")
Fixes tag
Fixes: b471f2f1de8 ("bpf: implement MAP_GET_NEXT_KEY command for LPM_TRIE")
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
or later) just making sure it is not set (or set to "auto").
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-06-11 10:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 10:05 Stephen Rothwell [this message]
2019-06-12 14:58 ` linux-next: Fixes tag needs some work in the bpf tree Daniel Borkmann
-- strict thread matches above, loose matches on Subject: below --
2019-06-26 22:05 Stephen Rothwell
2019-06-26 22:13 ` Roman Gushchin
2019-06-26 23:36 ` Alexei Starovoitov
2019-06-26 23:43 ` Roman Gushchin
2019-06-27 1:45 ` Stephen Rothwell
2019-06-27 22:25 ` Daniel Borkmann
2019-06-27 22:43 ` Roman Gushchin
2021-08-23 22:08 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=20190611200556.4a09514d@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=ast@kernel$(echo .)org \
--cc=daniel@iogearbox$(echo .)net \
--cc=jonathan.lemon@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
/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