From: David Miller <davem@davemloft.net>
To: ast@fb.com
Cc: daniel@iogearbox.net, jannh@google.com,
torvalds@linux-foundation.org, netdev@vger.kernel.org,
kernel-team@fb.com
Subject: Re: [PATCH net 0/3] bpf: fix several bugs
Date: Thu, 28 Apr 2016 17:30:18 -0400 (EDT) [thread overview]
Message-ID: <20160428.173018.367287857434534642.davem@davemloft.net> (raw)
In-Reply-To: <1461808582-1452466-1-git-send-email-ast@fb.com>
From: Alexei Starovoitov <ast@fb.com>
Date: Wed, 27 Apr 2016 18:56:19 -0700
> First two patches address bugs found by Jann Horn.
> Last patch is a minor samples fix spotted during the testing.
Series applied and queued up for -stable, thanks.
prev parent reply other threads:[~2016-04-28 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 1:56 [PATCH net 0/3] bpf: fix several bugs Alexei Starovoitov
2016-04-28 1:56 ` [PATCH net 1/3] bpf: fix refcnt overflow Alexei Starovoitov
2016-04-28 1:56 ` [PATCH net 2/3] bpf: fix check_map_func_compatibility logic Alexei Starovoitov
2016-04-28 9:31 ` Jann Horn
2016-04-28 1:56 ` [PATCH net 3/3] samples/bpf: fix trace_output example Alexei Starovoitov
2016-04-28 21:30 ` 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=20160428.173018.367287857434534642.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=jannh@google.com \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.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).