From: "Mickaël Salaün" <mic@digikod.net>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, acme@redhat.com,
netdev@vger.kernel.org, ast@fb.com, daniel@iogearbox.net,
shuah@kernel.org
Subject: Re: [PATCH net-next v2 1/8] bpf: Use bpf_load_program() from the library
Date: Tue, 7 Feb 2017 21:37:33 +0100 [thread overview]
Message-ID: <765bfbc6-8953-7e53-125b-cfe15e2171c3@digikod.net> (raw)
In-Reply-To: <20170207.133551.1797238908531958057.davem@davemloft.net>
[-- Attachment #1.1: Type: text/plain, Size: 380 bytes --]
Right, it was a batch of miscellaneous patches at first but I split them
in three series. I'm going to resend this patches in two v3 series (with
cover letters): one for each tree (net-next and perf).
Thanks,
Mickaël
On 07/02/2017 19:35, David Miller wrote:
>
> Please post your patch series(s) with proper "[PATCH ... 0/N]" header postings.
>
> Thank you.
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2017-02-07 20:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 22:49 Mickaël Salaün
2017-02-06 22:49 ` [PATCH net-next v2 2/8] bpf: Use bpf_map_update_elem() " Mickaël Salaün
2017-02-06 22:49 ` [PATCH net-next v2 3/8] bpf: Use bpf_map_lookup_elem() " Mickaël Salaün
2017-02-06 22:49 ` [PATCH net-next v2 4/8] bpf: Use bpf_map_delete_elem() " Mickaël Salaün
2017-02-06 22:49 ` [PATCH net-next v2 5/8] bpf: Use bpf_map_get_next_key() " Mickaël Salaün
2017-02-06 22:49 ` [PATCH net-next v2 6/8] bpf: Use bpf_create_map() " Mickaël Salaün
2017-02-06 22:49 ` [PATCH net-next v2 7/8] bpf: Remove bpf_sys.h from selftests Mickaël Salaün
2017-02-06 22:49 ` [PATCH net-next v2 8/8] bpf: Add test_tag to .gitignore Mickaël Salaün
2017-02-07 18:35 ` [PATCH net-next v2 1/8] bpf: Use bpf_load_program() from the library David Miller
2017-02-07 20:37 ` Mickaël Salaün [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=765bfbc6-8953-7e53-125b-cfe15e2171c3@digikod.net \
--to=mic@digikod.net \
--cc=acme@redhat.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shuah@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
all inboxes | Powered by JetHome®