From: Bowers, AndrewX <andrewx.bowers@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next v1 3/3] i40evf: disable unused flags
Date: Tue, 2 May 2017 19:17:36 +0000 [thread overview]
Message-ID: <26D9FDECA4FBDD4AADA65D8E2FC68A4A10DA1F6C@ORSMSX104.amr.corp.intel.com> (raw)
In-Reply-To: <1493423597-18306-4-git-send-email-jesse.brandeburg@intel.com>
> -----Original Message-----
> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at lists.osuosl.org] On
> Behalf Of Jesse Brandeburg
> Sent: Friday, April 28, 2017 4:53 PM
> To: intel-wired-lan at lists.osuosl.org
> Subject: [Intel-wired-lan] [PATCH net-next v1 3/3] i40evf: disable unused
> flags
>
> The i40evf hardware doesn't have any way to ever report FCoE enabled so
> just force the code to always report FCoE is disabled, remove the unused
> defines, and mark the OP as reserved.
>
> Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
> ---
> drivers/net/ethernet/intel/i40evf/i40e_common.c | 3 +--
> drivers/net/ethernet/intel/i40evf/i40e_virtchnl.h | 3 +--
> 2 files changed, 2 insertions(+), 4 deletions(-)
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
next prev parent reply other threads:[~2017-05-02 19:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 23:53 [Intel-wired-lan] [PATCH net-next v1 0/3] i40e/i40evf: small fixes Jesse Brandeburg
2017-04-28 23:53 ` [Intel-wired-lan] [PATCH net-next v1 1/3] i40evf: fix duplicate lines Jesse Brandeburg
2017-04-28 23:53 ` [Intel-wired-lan] [PATCH net-next v1 2/3] i40evf: fix merge error in older patch Jesse Brandeburg
2017-04-28 23:53 ` [Intel-wired-lan] [PATCH net-next v1 3/3] i40evf: disable unused flags Jesse Brandeburg
2017-05-02 19:17 ` Bowers, AndrewX [this message]
2017-05-02 19:17 ` [Intel-wired-lan] [PATCH net-next v1 2/3] i40evf: fix merge error in older patch Bowers, AndrewX
2017-05-02 19:16 ` [Intel-wired-lan] [PATCH net-next v1 1/3] i40evf: fix duplicate lines 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=26D9FDECA4FBDD4AADA65D8E2FC68A4A10DA1F6C@ORSMSX104.amr.corp.intel.com \
--to=andrewx.bowers@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.