From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH V0] i40e: Program device correctly as part of adding flow director entry
Date: Wed, 27 Jul 2016 08:53:33 -0700 [thread overview]
Message-ID: <1469634813.2232.14.camel@intel.com> (raw)
In-Reply-To: <1469598563-42383-1-git-send-email-kiran.patil@intel.com>
On Tue, 2016-07-26 at 22:49 -0700, Kiran Patil wrote:
> This patch fixes the problem where driver was not programming
> underlying device correctly when user specifies less than full tuple
> set as part of adding flow director entry (for flow-type tcp4/udp4)
> using ethtool.
>
> Signed-off-by: Kiran Patil <kiran.patil@intel.com>
> Change-Id: I90052508f8c172c0da5a4b78b949704b4a59ea78
> Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
> ---
> ?drivers/net/ethernet/intel/i40e/i40e_ethtool.c | 116
> +++++++++++++++++++++++++
> ?1 file changed, 116 insertions(+)
For public consumption, dropping this patch because a different approach is
being taken to resolve this issue.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20160727/a3cc89db/attachment.asc>
prev parent reply other threads:[~2016-07-27 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 5:49 [Intel-wired-lan] [PATCH V0] i40e: Program device correctly as part of adding flow director entry Kiran Patil
2016-07-27 6:01 ` Jeff Kirsher
2016-07-27 15:52 ` Wyborny, Carolyn
2016-08-02 18:25 ` John Fastabend
2016-08-02 19:16 ` Patil, Kiran
2016-07-27 15:53 ` Jeff Kirsher [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=1469634813.2232.14.camel@intel.com \
--to=jeffrey.t.kirsher@intel.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 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.