From: Daniel Borkmann <daniel@iogearbox.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
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: Re: linux-next: Fixes tag needs some work in the bpf tree
Date: Wed, 12 Jun 2019 16:58:41 +0200 [thread overview]
Message-ID: <0918037f-bc79-394a-bdbc-88e70989436b@iogearbox.net> (raw)
In-Reply-To: <20190611200556.4a09514d@canb.auug.org.au>
On 06/11/2019 12:05 PM, Stephen Rothwell wrote:
> 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").
>
Fyi, fixed this up yesterday in bpf tree, thanks.
next prev parent reply other threads:[~2019-06-12 14:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 10:05 linux-next: Fixes tag needs some work in the bpf tree Stephen Rothwell
2019-06-12 14:58 ` Daniel Borkmann [this message]
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=0918037f-bc79-394a-bdbc-88e70989436b@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=jonathan.lemon@gmail.com \
--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).