From: Stephen Hemminger <stephen@networkplumber.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, jhs@mojatatu.com
Subject: Re: [patch iproute2 repost 1/2] tc: push bpf common code into separate file
Date: Thu, 5 Feb 2015 10:39:17 -0800 [thread overview]
Message-ID: <20150205103917.0378191f@urahara> (raw)
In-Reply-To: <1421682990-11072-1-git-send-email-jiri@resnulli.us>
On Mon, 19 Jan 2015 16:56:29 +0100
Jiri Pirko <jiri@resnulli.us> wrote:
> Signed-off-by: Jiri Pirko <jiri@resnulli.us>
Both patches applied to net-next branch.
prev parent reply other threads:[~2015-02-05 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 15:56 [patch iproute2 repost 1/2] tc: push bpf common code into separate file Jiri Pirko
2015-01-19 15:56 ` [patch iproute2 repost 2/2] tc: add support for BPF based actions Jiri Pirko
2015-02-05 18:39 ` 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=20150205103917.0378191f@urahara \
--to=stephen@networkplumber.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--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