From: Greg KH <greg@kroah.com>
To: Matt Domsch <Matt_Domsch@Dell.com>
Cc: "K, Narendra" <Narendra_K@Dell.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-hotplug@vger.kernel.org" <linux-hotplug@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"Hargrave, Jordan" <Jordan_Hargrave@Dell.com>,
"Rose, Charles" <Charles_Rose@Dell.com>,
"Nijhawan, Vijay" <Vijay_Nijhawan@Dell.com>
Subject: Re: [PATCH 1/2] Export firmware assigned labels of network devices to sysfs
Date: Wed, 9 Jun 2010 08:02:40 -0700 [thread overview]
Message-ID: <20100609150240.GA20705@kroah.com> (raw)
In-Reply-To: <20100609041709.GA7280@auslistsprd01.us.dell.com>
On Tue, Jun 08, 2010 at 11:17:09PM -0500, Matt Domsch wrote:
> On Fri, May 28, 2010 at 11:51:40PM -0500, Domsch, Matt wrote:
> > On Fri, May 28, 2010 at 05:27:45PM -0500, Greg KH wrote:
> > > Care to post that ECN publically? And no, the Linux Foundation does not
> > > have a PCI-SIG membership, the PCI-SIG keeps forbidding it. Other
> > > operating systems are allowed to join but not Linux. Strange but
> > > true...
> >
> > I'm looking into it, and should know more next week.
>
> I'm advised that I cannot post the ECN publically, due to it being an
> in-progress work item of a SIG working group, and therefore falls
> under the confidentiality rules that SIG members agree to. Members of
> the PCI SIG have access, which unfortunately is not everyone.
Then we can't properly review this, sorry. How about waiting until the
ECN is finalized? Then we could review and possibly accept this.
thanks,
greg k-h
next prev parent reply other threads:[~2010-06-09 15:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 11:55 [PATCH 1/2] Export firmware assigned labels of network devices to sysfs K, Narendra
2010-05-28 13:16 ` Domsch, Matt
2010-05-28 15:40 ` Greg KH
2010-05-28 18:11 ` Matt Domsch
2010-05-28 22:27 ` Greg KH
2010-05-29 4:51 ` Domsch, Matt
2010-06-09 4:17 ` Matt Domsch
2010-06-09 15:02 ` Greg KH [this message]
2010-05-31 7:55 ` Narendra_K
2010-05-31 14:07 ` Michael Ellerman
2010-05-31 18:42 ` Narendra_K
2010-06-02 23:54 ` Michael Ellerman
[not found] <EDA0A4495861324DA2618B4C45DCB3EE612AB6@blrx3m08.blr.amer.dell.com>
2010-06-29 16:28 ` Narendra K
2010-06-30 15:42 ` Greg KH
[not found] <EDA0A4495861324DA2618B4C45DCB3EE612B1B@blrx3m08.blr.amer.dell.com>
2010-07-06 18:52 ` Narendra K
2010-07-06 23:22 ` Greg KH
[not found] <EDA0A4495861324DA2618B4C45DCB3EE612B27@blrx3m08.blr.amer.dell.com>
2010-07-07 17:48 ` Narendra K
2010-07-07 18:11 ` Greg KH
2010-07-07 18:35 ` Domsch, Matt
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=20100609150240.GA20705@kroah.com \
--to=greg@kroah.com \
--cc=Charles_Rose@Dell.com \
--cc=Jordan_Hargrave@Dell.com \
--cc=Matt_Domsch@Dell.com \
--cc=Narendra_K@Dell.com \
--cc=Vijay_Nijhawan@Dell.com \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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).