From: David Miller <davem@davemloft.net>
To: kafai@fb.com
Cc: netdev@vger.kernel.org, ast@fb.com, daniel@iogearbox.net,
kernel-team@fb.com
Subject: Re: [PATCH net-next 0/3] bpf: Misc improvements and a new usage on bpf obj name
Date: Sat, 07 Oct 2017 23:29:58 +0100 (WEST) [thread overview]
Message-ID: <20171007.232958.1046556399820886279.davem@davemloft.net> (raw)
In-Reply-To: <20171006045213.752372-1-kafai@fb.com>
From: Martin KaFai Lau <kafai@fb.com>
Date: Thu, 5 Oct 2017 21:52:10 -0700
> The first two patches make improvements on the bpf obj name.
>
> The last patch adds the prog name to kallsyms.
Series applied, thanks Martin.
prev parent reply other threads:[~2017-10-07 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 4:52 [PATCH net-next 0/3] bpf: Misc improvements and a new usage on bpf obj name Martin KaFai Lau
2017-10-06 4:52 ` [PATCH net-next 1/3] bpf: Change bpf_obj_name_cpy() to better ensure map's name is init by 0 Martin KaFai Lau
2017-10-06 4:52 ` [PATCH net-next 2/3] bpf: Use char in prog and map name Martin KaFai Lau
2017-10-06 4:52 ` [PATCH net-next 3/3] bpf: Append prog->aux->name in bpf_get_prog_name() Martin KaFai Lau
2017-10-07 22:29 ` 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=20171007.232958.1046556399820886279.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--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).