From: Daniel Borkmann <daniel@iogearbox.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: ast@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 -master 0/4] Minor BPF updates on frontend
Date: Tue, 02 Feb 2016 10:22:52 +0100 [thread overview]
Message-ID: <56B0756C.4060303@iogearbox.net> (raw)
In-Reply-To: <20160202160745.6ff0fcaa@samsung9>
Hi Stephen,
On 02/02/2016 06:07 AM, Stephen Hemminger wrote:
> On Tue, 2 Feb 2016 01:12:25 +0100
> Daniel Borkmann <daniel@iogearbox.net> wrote:
>
>> Couple of minor updates on tc frontend.
>>
>> Stephen, the patches are against iproute2 -master branch and *on top of*
>> the two that are already lingering in patchwork:
>>
>> - http://patchwork.ozlabs.org/patch/569923/
>
> Some cruft snuck into that patch so it is still in "Changes requested"
As stated earlier, that patch is okay as-is. No cruft snuck
in anywhere ...
>> - http://patchwork.ozlabs.org/patch/571385/
> This one is applied
Ok, thanks. I presume locally as it's not pushed out yet.
Also replying to your answer on patch 2/4 here: Doesn't apply of
course as the first dependency patch is in 'Changes Requested'.
Otherwise, it applies just fine.
Thanks!
prev parent reply other threads:[~2016-02-02 9:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 0:12 [PATCH iproute2 -master 0/4] Minor BPF updates on frontend Daniel Borkmann
2016-02-02 0:12 ` [PATCH iproute2 -master 1/4] tc, bpf, examples: further bpf_api improvements Daniel Borkmann
2016-02-02 0:12 ` [PATCH iproute2 -master 2/4] tc, bpf: improve verifier logging Daniel Borkmann
2016-02-02 0:51 ` John Fastabend
2016-02-02 5:02 ` Stephen Hemminger
2016-02-02 0:12 ` [PATCH iproute2 -master 3/4] tc, bpf: give some more hints wrt false relos Daniel Borkmann
2016-02-02 0:12 ` [PATCH iproute2 -master 4/4] tc, bpf: use bind/type macros from gelf Daniel Borkmann
2016-02-02 5:07 ` [PATCH iproute2 -master 0/4] Minor BPF updates on frontend Stephen Hemminger
2016-02-02 9:22 ` Daniel Borkmann [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=56B0756C.4060303@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.