From: John Fastabend <john.fastabend@gmail.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v2 net-next 1/3] net: ixgbe: fix error handling in tc cls_u32 offload routines.
Date: Mon, 07 Mar 2016 11:29:27 -0800 [thread overview]
Message-ID: <56DDD697.4020700@gmail.com> (raw)
In-Reply-To: <1457372509-3135-1-git-send-email-sridhar.samudrala@intel.com>
On 16-03-07 09:41 AM, Sridhar Samudrala wrote:
> Check for handle ids when adding/deleting hash nodes OR adding/deleting
> filter entries and limit them to max number of links or header nodes
> supported(IXGBE_MAX_LINK_HANDLE).
>
> Start from bit 0 when setting hash table bit-map.(adapter->tables)
>
> Signed-off-by: Sridhar Samudrala <sridhar.samudrala@intel.com>
>
> ---
>
Looks good.
Acked-by: John Fastabend <john.r.fastabend@intel.com>
next prev parent reply other threads:[~2016-03-07 19:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 17:41 [Intel-wired-lan] [PATCH v2 net-next 1/3] net: ixgbe: fix error handling in tc cls_u32 offload routines Sridhar Samudrala
2016-03-07 17:41 ` [Intel-wired-lan] [PATCH v2 net-next 2/3] net: ixgbe: Fix cls_u32 offload support for fields with masks Sridhar Samudrala
2016-03-07 19:30 ` John Fastabend
2016-03-08 23:08 ` Bowers, AndrewX
2016-03-07 17:41 ` [Intel-wired-lan] [PATCH v2 net-next 3/3] net: ixgbe: Fix cls_u32 offload support for L4 ports Sridhar Samudrala
2016-03-07 19:31 ` John Fastabend
2016-03-07 19:29 ` John Fastabend [this message]
2016-03-08 23:09 ` [Intel-wired-lan] [PATCH v2 net-next 1/3] net: ixgbe: fix error handling in tc cls_u32 offload routines Bowers, AndrewX
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=56DDD697.4020700@gmail.com \
--to=john.fastabend@gmail.com \
--cc=intel-wired-lan@osuosl.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