From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: netdev@vger.kernel.org
Cc: john.r.fastabend@intel.com, sridhar.samudrala@intel.com,
Jakub Kicinski <jakub.kicinski@netronome.com>
Subject: [PATCH net 0/2] incremental cls_u32 hardware offload fixes
Date: Wed, 8 Jun 2016 20:11:02 +0100 [thread overview]
Message-ID: <1465413064-32196-1-git-send-email-jakub.kicinski@netronome.com> (raw)
These are incremental changes from v1 of cls_u32 fixes.
First patch is reposted in its entirety, patch 2 is an
incremental change from patch 2 of the original series.
Jakub Kicinski (2):
net: cls_u32: catch all hardware offload errors
net: cls_u32: be more strict about skip-sw flag (knode part)
net/sched/cls_u32.c | 45 ++++++++++++++++++++++++++-------------------
1 file changed, 26 insertions(+), 19 deletions(-)
--
1.9.1
next reply other threads:[~2016-06-08 19:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 19:11 Jakub Kicinski [this message]
2016-06-08 19:11 ` [PATCH net 1/2] net: cls_u32: catch all hardware offload errors Jakub Kicinski
2016-06-08 19:11 ` [PATCH net 2/2] net: cls_u32: be more strict about skip-sw flag for knodes Jakub Kicinski
2016-06-09 4:43 ` [PATCH net 0/2] incremental cls_u32 hardware offload fixes David Miller
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=1465413064-32196-1-git-send-email-jakub.kicinski@netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sridhar.samudrala@intel.com \
/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).