From: David Miller <davem@davemloft.net>
To: ast@kernel.org
Cc: daniel@iogearbox.net, netdev@vger.kernel.org,
bpf@vger.kernel.org, kernel-team@fb.com
Subject: Re: pull-request: bpf 2019-12-05
Date: Fri, 06 Dec 2019 00:04:31 -0800 (PST) [thread overview]
Message-ID: <20191206.000431.1823406760870683874.davem@davemloft.net> (raw)
In-Reply-To: <20191206061857.3660737-1-ast@kernel.org>
From: Alexei Starovoitov <ast@kernel.org>
Date: Thu, 5 Dec 2019 22:18:57 -0800
> The following pull-request contains BPF updates for your *net* tree.
>
> We've added 6 non-merge commits during the last 1 day(s) which contain
> a total of 14 files changed, 116 insertions(+), 37 deletions(-).
>
> The main changes are:
>
> 1) three selftests fixes, from Stanislav.
>
> 2) one samples fix, from Jesper.
>
> 3) one verifier fix, from Yonghong.
>
> Please consider pulling these changes from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git
Pulled, thanks Alexei.
prev parent reply other threads:[~2019-12-06 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 6:18 pull-request: bpf 2019-12-05 Alexei Starovoitov
2019-12-06 8:04 ` 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=20191206.000431.1823406760870683874.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--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).