From: Keller, Jacob E <jacob.e.keller@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH V4 2/2] ixgbe: Add support for VXLAN RX offloads
Date: Fri, 21 Aug 2015 22:18:59 +0000 [thread overview]
Message-ID: <1440195539.10719.8.camel@intel.com> (raw)
In-Reply-To: <305E19FFAC908240AB6DEBD1E2D8C1E180BA1A83@ORSMSX108.amr.corp.intel.com>
On Mon, 2015-08-17 at 21:17 +0000, Schmitt, Phillip J wrote:
>
> > -----Original Message-----
> > From: Intel-wired-lan [mailto:
> > intel-wired-lan-bounces at lists.osuosl.org] On
> > Behalf Of Mark D Rustad
> > Sent: Monday, June 15, 2015 11:33 AM
> > To: intel-wired-lan at lists.osuosl.org
> > Subject: [Intel-wired-lan] [PATCH V4 2/2] ixgbe: Add support for
> > VXLAN RX
> > offloads
> >
> > From: Mark Rustad <mark.d.rustad@intel.com>
> >
> > Add support for VXLAN RX offloads for the X55x devices that support
> > them.
> >
> > Signed-off-by: Mark Rustad <mark.d.rustad@intel.com>
> > ---
> > Changes in V3:
> > - change __constant_htons to simply htons
>
> Changes in V4:
> > - add static to ixgbe_clear_vxlan_port
> > - use ixgbe_clear_vxlan_port to clear vxlan port
> > - call ixgbe_clear_vxlan_port when turning checksum offload off
> > ---
>
>
> Tested-by: Phil Schmitt <phillip.j.schmitt@intel.com>
This patch causes a build failure with CONFIG_IXGBE_VXLAN enabled,
since we already include <net/vxlan.h> which for some reason isn't
protected by a dual-include #ifndef header check.
Regards,
Jake
prev parent reply other threads:[~2015-08-21 22:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 18:33 [Intel-wired-lan] [PATCH V4 0/2] ixgbe: Add support for VXLAN RX offloads Mark D Rustad
2015-06-15 18:33 ` [Intel-wired-lan] [PATCH V4 1/2] ixgbe: Add support for UDP-encapsulated tx checksum offload Mark D Rustad
2015-08-17 21:16 ` Schmitt, Phillip J
2015-06-15 18:33 ` [Intel-wired-lan] [PATCH V4 2/2] ixgbe: Add support for VXLAN RX offloads Mark D Rustad
2015-08-17 21:17 ` Schmitt, Phillip J
2015-08-21 22:18 ` Keller, Jacob E [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=1440195539.10719.8.camel@intel.com \
--to=jacob.e.keller@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.