From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: ast@kernel.org, netdev@vger.kernel.org
Subject: Re: pull-request: bpf-next 2018-11-26
Date: Mon, 26 Nov 2018 13:11:21 -0800 (PST) [thread overview]
Message-ID: <20181126.131121.902156280041340396.davem@davemloft.net> (raw)
In-Reply-To: <20181126132528.4969-1-daniel@iogearbox.net>
From: Daniel Borkmann <daniel@iogearbox.net>
Date: Mon, 26 Nov 2018 14:25:28 +0100
> The following pull-request contains BPF updates for your *net-next* tree.
...
> Please consider pulling these changes from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git
>
> Note, there is a tiny merge conflict in BPF's kselftest Makefile.
> Resolution is to take both chunks, like:
>
> [...]
> test_sk_lookup_kern.o test_xdp_vlan.o test_queue_map.o test_stack_map.o \
> xdp_dummy.o test_map_in_map.o
Pulled, thanks!
prev parent reply other threads:[~2018-11-27 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 13:25 pull-request: bpf-next 2018-11-26 Daniel Borkmann
2018-11-26 21:11 ` David Miller [this message]
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=20181126.131121.902156280041340396.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--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).