From: Ben Hutchings <bhutchings@solarflare.com>
To: Yi Zou <yi.zou@intel.com>
Cc: netdev@vger.kernel.org, devel@open-fcoe.org
Subject: Re: [PATCH 2/2] net: define feature flags for FCoE offloads
Date: Mon, 06 Oct 2008 23:37:22 +0100 [thread overview]
Message-ID: <1223332642.3984.94.camel@achroite> (raw)
In-Reply-To: <20081006220926.3308.48505.stgit@zyfc9ini.jf.intel.com>
On Mon, 2008-10-06 at 15:09 -0700, Yi Zou wrote:
> From: Chris Leech <christopher.leech@intel.com>
>
> Signed-off-by: Chris Leech <christopher.leech@intel.com>
> Signed-off-by: Yi Zou <yi.zou@intel.com>
> ---
>
> include/linux/netdevice.h | 3 +++
> include/linux/skbuff.h | 2 ++
> 2 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
> index 9cfd20b..ef65927 100644
> --- a/include/linux/netdevice.h
> +++ b/include/linux/netdevice.h
> @@ -522,6 +522,8 @@ struct net_device
> #define NETIF_F_NETNS_LOCAL 8192 /* Does not change network namespaces */
> #define NETIF_F_LRO 32768 /* large receive offload */
>
> +#define NETIF_F_FCOE_CRC (1 << 24) /* FCoE CRC32 */
> +
> /* Segmentation offload features */
> #define NETIF_F_GSO_SHIFT 16
> #define NETIF_F_GSO_MASK 0xffff0000
[...]
NETIF_F_FCOE_CRC shouldn't be included in NETIF_F_GSO_MASK.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2008-10-06 22:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 22:09 [PATCH 0/2] New flags for Fibre Channel over Ethernet (FCoE) Yi Zou
[not found] ` <20081006220524.3308.64889.stgit-23BaheqE+Bznoz6Kjl9f4RL4W9x8LtSr@public.gmane.org>
2008-10-06 22:09 ` [PATCH 1/2] net: add ETH_P_FCOE " Yi Zou
2008-10-06 22:33 ` Roland Dreier
2008-10-06 23:11 ` Zou, Yi
2008-10-06 22:09 ` [PATCH 2/2] net: define feature flags for FCoE offloads Yi Zou
2008-10-06 22:37 ` Ben Hutchings [this message]
2008-10-06 23:13 ` Zou, Yi
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=1223332642.3984.94.camel@achroite \
--to=bhutchings@solarflare.com \
--cc=devel@open-fcoe.org \
--cc=netdev@vger.kernel.org \
--cc=yi.zou@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 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.