From: Johannes Berg <johannes@sipsolutions.net>
To: netdev@vger.kernel.org
Cc: alexei.starovoitov@gmail.com
Subject: Re: [PATCH net-next v3 2/2] bpf: remove struct bpf_map_type_list
Date: Tue, 11 Apr 2017 15:29:18 +0200 [thread overview]
Message-ID: <1491917358.31620.28.camel@sipsolutions.net> (raw)
In-Reply-To: <20170410124431.4305-3-johannes@sipsolutions.net> (sfid-20170410_144515_702266_3C441074)
0-day found a linking problem with this, I'll resubmit later.
johannes
prev parent reply other threads:[~2017-04-11 13:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 12:44 [PATCH net-next v3 0/2] bpf: prog/map type reductions Johannes Berg
2017-04-10 12:44 ` [PATCH net-next v3 1/2] bpf: remove struct bpf_prog_type_list Johannes Berg
2017-04-10 14:56 ` Alexei Starovoitov
2017-04-10 16:00 ` Daniel Borkmann
2017-04-10 12:44 ` [PATCH net-next v3 2/2] bpf: remove struct bpf_map_type_list Johannes Berg
2017-04-10 14:58 ` Alexei Starovoitov
2017-04-10 16:06 ` Daniel Borkmann
2017-04-11 13:29 ` Johannes Berg [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=1491917358.31620.28.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=alexei.starovoitov@gmail.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).