All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Cree <ecree@solarflare.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v5 3/3] ixgbe: Add new ndo to trust VF
Date: Wed, 27 May 2015 18:04:27 +0100	[thread overview]
Message-ID: <5565F91B.8080405@solarflare.com> (raw)
In-Reply-To: <C5551D9AAB213A418B7FD5E4A6F30A07892FD632@ORSMSX108.amr.corp.intel.com>

On 27/05/15 16:55, Rose, Gregory V wrote:
> There's nothing to prevent any vendor from notifying a VF that it has privileges and there's nothing that require that they do.  This should be a vendor specific detail.
Agreed - purely a driver implementation detail.
> So now that I've stated my preference let me also state that I do not want to hold up acceptance of the Hiroshi's if_link patch that sets the trusted/privileged state for the VF while we further discuss this driver specific detail.
Agreed.
The information contained in this message is confidential and is intended for the addressee(s) only. If you have received this message in error, please notify the sender immediately and delete the message. Unless you are an addressee (or authorized to receive for an addressee), you may not use, copy or disclose to anyone this message or any information contained in this message. The unauthorized use, disclosure, copying or alteration of this message is strictly prohibited.

WARNING: multiple messages have this Message-ID (diff)
From: Edward Cree <ecree@solarflare.com>
To: "Rose, Gregory V" <gregory.v.rose@intel.com>
Cc: "Skidmore, Donald C" <donald.c.skidmore@intel.com>,
	Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>,
	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>,
	"nhorman@redhat.com" <nhorman@redhat.com>,
	"jogreene@redhat.com" <jogreene@redhat.com>,
	"Linux Netdev List" <netdev@vger.kernel.org>,
	"Choi, Sy Jong" <sy.jong.choi@intel.com>,
	Rony Efraim <ronye@mellanox.com>,
	David Miller <davem@davemloft.net>,
	Or Gerlitz <gerlitz.or@gmail.com>,
	"sassmann@redhat.com" <sassmann@redhat.com>
Subject: Re: [PATCH v5 3/3] ixgbe: Add new ndo to trust VF
Date: Wed, 27 May 2015 18:04:27 +0100	[thread overview]
Message-ID: <5565F91B.8080405@solarflare.com> (raw)
In-Reply-To: <C5551D9AAB213A418B7FD5E4A6F30A07892FD632@ORSMSX108.amr.corp.intel.com>

On 27/05/15 16:55, Rose, Gregory V wrote:
> There's nothing to prevent any vendor from notifying a VF that it has privileges and there's nothing that require that they do.  This should be a vendor specific detail.
Agreed - purely a driver implementation detail.
> So now that I've stated my preference let me also state that I do not want to hold up acceptance of the Hiroshi's if_link patch that sets the trusted/privileged state for the VF while we further discuss this driver specific detail.
Agreed.

  reply	other threads:[~2015-05-27 17:04 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20  0:06 [Intel-wired-lan] [PATCH v5 3/3] ixgbe: Add new ndo to trust VF Hiroshi Shimamoto
2015-05-20  0:06 ` Hiroshi Shimamoto
2015-05-20 18:14 ` [Intel-wired-lan] " Skidmore, Donald C
2015-05-20 18:14   ` Skidmore, Donald C
2015-05-21  4:12   ` [Intel-wired-lan] " Hiroshi Shimamoto
2015-05-21  4:12     ` Hiroshi Shimamoto
2015-05-21 17:08     ` [Intel-wired-lan] " Skidmore, Donald C
2015-05-21 17:08       ` Skidmore, Donald C
2015-05-22  2:31       ` [Intel-wired-lan] " Hiroshi Shimamoto
2015-05-22  2:31         ` Hiroshi Shimamoto
2015-05-22 15:07         ` [Intel-wired-lan] " Rose, Gregory V
2015-05-22 15:07           ` Rose, Gregory V
2015-05-22 17:51           ` [Intel-wired-lan] " Skidmore, Donald C
2015-05-22 17:51             ` Skidmore, Donald C
2015-05-26  0:59             ` [Intel-wired-lan] " Hiroshi Shimamoto
2015-05-26  0:59               ` Hiroshi Shimamoto
2015-05-26 17:45               ` [Intel-wired-lan] " Skidmore, Donald C
2015-05-26 17:45                 ` Skidmore, Donald C
2015-05-26 18:03                 ` [Intel-wired-lan] " Rose, Gregory V
2015-05-26 18:03                   ` Rose, Gregory V
2015-05-27  0:27                   ` [Intel-wired-lan] " Hiroshi Shimamoto
2015-05-27  0:27                     ` Hiroshi Shimamoto
2015-05-27  2:00                     ` [Intel-wired-lan] " Rose, Gregory V
2015-05-27  2:00                       ` Rose, Gregory V
2015-05-27 16:00                       ` [Intel-wired-lan] " Skidmore, Donald C
2015-05-27 16:00                         ` Skidmore, Donald C
2015-05-27 16:19                         ` [Intel-wired-lan] " Rose, Gregory V
2015-05-27 16:19                           ` Rose, Gregory V
2015-06-15 10:39                         ` [Intel-wired-lan] " Hiroshi Shimamoto
2015-06-15 10:39                           ` Hiroshi Shimamoto
2015-05-27  9:03                     ` [Intel-wired-lan] " Edward Cree
2015-05-27  9:03                       ` Edward Cree
2015-05-27 15:34                       ` [Intel-wired-lan] " Skidmore, Donald C
2015-05-27 15:34                         ` Skidmore, Donald C
2015-05-27 15:55                         ` [Intel-wired-lan] " Rose, Gregory V
2015-05-27 15:55                           ` Rose, Gregory V
2015-05-27 17:04                           ` Edward Cree [this message]
2015-05-27 17:04                             ` Edward Cree

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=5565F91B.8080405@solarflare.com \
    --to=ecree@solarflare.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.