From: Stefan Assmann <sassmann@kpanic.de>
To: intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, davem@davemloft.net,
jeffrey.t.kirsher@intel.com, sassmann@kpanic.de
Subject: [PATCH 0/2] i40e/i40evf: fix override of administratively set MAC address in trusted mode
Date: Thu, 29 Jun 2017 15:12:23 +0200 [thread overview]
Message-ID: <20170629131225.9251-1-sassmann@kpanic.de> (raw)
In trusted mode VFs should be able to override the administratively set MAC
address. This is currently not possible as i40evf returns -EPERM if an
administratively set MAC is present, for MAC change requests.
First patch renames vf_offload_flags to vf_cap_flags to make it more generic.
Second patch then adds a flag to vf_cap_flags to give the VF information on
whether it runs in trusted mode and makes use of the flag in i40evf.
Patches are against jkirshers dev-queue branch.
Stefan Assmann (2):
i40e/i40evf: rename vf_offload_flags to vf_cap_flags in struct
virtchnl_vf_resource
i40e/i40evf: add virtchnl flag to indicate trusted VF
drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c | 25 ++++++++++++----------
drivers/net/ethernet/intel/i40evf/i40e_common.c | 2 +-
drivers/net/ethernet/intel/i40evf/i40evf.h | 10 ++++-----
drivers/net/ethernet/intel/i40evf/i40evf_main.c | 15 +++++++------
include/linux/avf/virtchnl.h | 5 +++--
5 files changed, 31 insertions(+), 26 deletions(-)
--
2.9.4
next reply other threads:[~2017-06-29 13:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 13:12 Stefan Assmann [this message]
2017-06-29 13:12 ` [PATCH 1/2] i40e/i40evf: rename vf_offload_flags to vf_cap_flags in struct virtchnl_vf_resource Stefan Assmann
2017-07-05 21:15 ` [Intel-wired-lan] " Wyborny, Carolyn
2017-07-06 14:24 ` Greg Rose
2017-07-06 15:26 ` Wyborny, Carolyn
2017-07-07 8:18 ` Greg Rose
2017-06-29 13:12 ` [PATCH 2/2] i40e/i40evf: add virtchnl flag to indicate trusted VF Stefan Assmann
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=20170629131225.9251-1-sassmann@kpanic.de \
--to=sassmann@kpanic.de \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).