From: Stephen Hemminger <stephen@networkplumber.org>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: netdev@vger.kernel.org, daniel@iogearbox.net
Subject: Re: [PATCH iproute2] tc: cls_bpf: handle skip_sw and skip_hw flags
Date: Mon, 17 Oct 2016 05:28:30 -0700 [thread overview]
Message-ID: <20161017052830.47de0a21@xeon-e3> (raw)
In-Reply-To: <1476287196-28931-1-git-send-email-jakub.kicinski@netronome.com>
On Wed, 12 Oct 2016 16:46:36 +0100
Jakub Kicinski <jakub.kicinski@netronome.com> wrote:
> Add support for controling hardware offload using (now standard)
> skip_sw and skip_hw flags in cls_bpf.
>
> Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Applied
prev parent reply other threads:[~2016-10-17 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 15:46 [PATCH iproute2] tc: cls_bpf: handle skip_sw and skip_hw flags Jakub Kicinski
2016-10-12 16:03 ` Daniel Borkmann
2016-10-13 9:06 ` Simon Horman
2016-10-17 12:28 ` 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=20161017052830.47de0a21@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=daniel@iogearbox.net \
--cc=jakub.kicinski@netronome.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).