From: Or Gerlitz <or.gerlitz@gmail.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: David Miller <davem@davemloft.net>,
Mitch Williams <mitch.a.williams@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"gospo@redhat.com" <gospo@redhat.com>,
"sassmann@redhat.com" <sassmann@redhat.com>,
Catherine Sullivan <catherine.sullivan@intel.com>
Subject: Re: [net-next 01/16] i40e: support VF link state ndo
Date: Mon, 17 Mar 2014 23:24:17 +0200 [thread overview]
Message-ID: <CAJZOPZLrwg2sMnhQZZhpjWdqjBEBuWujv0Uy9q-_bViK5j46zg@mail.gmail.com> (raw)
In-Reply-To: <1395060316-16897-2-git-send-email-jeffrey.t.kirsher@intel.com>
On Mon, Mar 17, 2014 at 2:45 PM, Jeff Kirsher
<jeffrey.t.kirsher@intel.com> wrote:
> From: Mitch Williams <mitch.a.williams@intel.com>
> This netdev op allows the PF driver to control the virtual link state of
> the VF devices. This can be used to deny naughty VF drivers access to the wire,
Does this denial exists in the patch or the current code? where?
Or.
next prev parent reply other threads:[~2014-03-17 21:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 12:45 [net-next 00/16][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2014-03-17 12:45 ` [net-next 01/16] i40e: support VF link state ndo Jeff Kirsher
2014-03-17 21:24 ` Or Gerlitz [this message]
2014-03-17 21:40 ` Williams, Mitch A
2014-03-17 12:45 ` [net-next 02/16] i40evf: correctly program RSS HLUT table Jeff Kirsher
2014-03-17 12:45 ` [net-next 03/16] i40evf: Support RSS option in ethtool Jeff Kirsher
2014-03-17 14:40 ` Or Gerlitz
2014-03-17 18:55 ` Williams, Mitch A
2014-03-17 21:19 ` Or Gerlitz
2014-03-17 18:53 ` Ben Hutchings
2014-03-17 18:55 ` Williams, Mitch A
2014-03-26 19:21 ` Williams, Mitch A
2014-03-28 0:14 ` Ben Hutchings
2014-03-28 17:05 ` Williams, Mitch A
2014-03-17 12:45 ` [net-next 04/16] i40evf: use min_t Jeff Kirsher
2014-03-17 12:45 ` [net-next 05/16] i40e: Patch to enable Ethtool/netdev feature flag for NTUPLE control Jeff Kirsher
2014-03-17 12:45 ` [net-next 06/16] i40e: Refactor and cleanup i40e_open(), adding i40e_vsi_open() Jeff Kirsher
2014-03-17 12:45 ` [net-next 07/16] i40e/i40evf: enable hardware feature head write back Jeff Kirsher
2014-03-17 12:45 ` [net-next 08/16] i40e/i40evf: reduce context descriptors Jeff Kirsher
2014-03-17 12:45 ` [net-next 09/16] i40e: potential array underflow in i40e_vc_process_vf_msg() Jeff Kirsher
2014-03-17 12:45 ` [net-next 10/16] i40e/i40evf: Bump build versions Jeff Kirsher
2014-03-17 12:45 ` [net-next 11/16] e1000e: Fix Hardware Unit Hang Jeff Kirsher
2014-03-17 12:45 ` [net-next 12/16] e1000e: Fix Explicitly set Transmit Control Register Jeff Kirsher
2014-03-17 12:45 ` [net-next 13/16] igb: Add register defines needed for time sync functions Jeff Kirsher
2014-03-17 12:45 ` [net-next 14/16] ixgbe: add ixgbe_write_pci_cfg_word with ixgbe_removed check Jeff Kirsher
2014-03-17 12:45 ` [net-next 15/16] ixgbevf: Indicate removal state explicitly Jeff Kirsher
2014-03-17 12:45 ` [net-next 16/16] ixgbevf: Protect ixgbevf_down with __IXGBEVF_DOWN bit Jeff Kirsher
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=CAJZOPZLrwg2sMnhQZZhpjWdqjBEBuWujv0Uy9q-_bViK5j46zg@mail.gmail.com \
--to=or.gerlitz@gmail.com \
--cc=catherine.sullivan@intel.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=mitch.a.williams@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sassmann@redhat.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 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).