linux-kernel - RE: [PATCH] drivers/firmware/edd: Treat "XPRS" host bus type the same as "PCI"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 28 Sep 2011 11:56:42 -0700
From:	"Zou, Yi" <yi.zou@...el.com>
To:	Michael Chan <mchan@...adcom.com>,
	Matt Domsch <Matt_Domsch@...l.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devel@...n-fcoe.org" <devel@...n-fcoe.org>
Subject: RE: [PATCH] drivers/firmware/edd: Treat "XPRS" host bus type the
 same as "PCI"

> 
> 
> On Wed, 2011-09-28 at 09:28 -0700, Matt Domsch wrote:
> > On Tue, Sep 27, 2011 at 05:32:08PM -0500, Michael Chan wrote:
> > > PCI Express devices will return "XPRS" host bus type during BIOS EDD
> > > call.  "XPRS" should be treated just like "PCI" so that the proper
> > > pci_dev symlink will be created.  Scripts such as fcoe-edd.sh will
> > > then work correctly.
> > >
> > > Cc: Matt Domsch <Matt_Domsch@...l.com>
> > > Signed-off-by: Michael Chan <mchan@...adcom.com>
> >
> > Agreed, this looks correct.  Thanks for the patch.  Feel free to
> > submit it through whichever maintainer tree is convenient for you.
> >
> > Reviewed-by: Matt Domsch <Matt_Domsch@...l.com>
> >
> 
> Yi, could you submit this patch through the open-fcoe tree?  Thanks.
> 
Sure, I will pull this into open-fcoe.org's tree and queue it up for next
push to scsi-misc as long as edd folks are ok with it. Just curious, this
is from edd4.0, so might be helpful to point that out in description...
I can fix that when I apply the patch to fcoe-next tree.


yi 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/