From: Stephen Hemminger <stephen@networkplumber.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: ast@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 -next] bpf: minor fix in api and bpf_dump_error() usage
Date: Thu, 17 Dec 2015 17:23:06 -0800 [thread overview]
Message-ID: <20151217172306.17bdb569@xeon-e3> (raw)
In-Reply-To: <6598a3bfadced14239ea333155eb7fb9aaceccda.1450108152.git.daniel@iogearbox.net>
On Mon, 14 Dec 2015 16:57:32 +0100
Daniel Borkmann <daniel@iogearbox.net> wrote:
> Fix a whitespace in bpf_dump_error() usage, and also a missing closing
> bracket in ntohl() macro for eBPF programs.
>
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
> ---
Applied to net-next
prev parent reply other threads:[~2015-12-18 1:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 15:57 [PATCH iproute2 -next] bpf: minor fix in api and bpf_dump_error() usage Daniel Borkmann
2015-12-18 1:23 ` Stephen Hemminger [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=20151217172306.17bdb569@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--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).