[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160126182259.GA15260@intel.com>
Date: Tue, 26 Jan 2016 10:23:00 -0800
From: "Veal, Bryan E." <bryan.e.veal@...el.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: Bjorn Helgaas <helgaas@...nel.org>,
Keith Busch <keith.busch@...el.com>,
"Derrick, Jonathan" <jonathan.derrick@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Bjorn Helgaas <bhelgaas@...gle.com>,
"Williams, Dan J" <dan.j.williams@...el.com>
Subject: Re: [PATCHv8 0/5] Driver for new "VMD" device
On Tue, Jan 26, 2016 at 08:46:09AM -0800, Christoph Hellwig wrote:
> On Wed, Jan 20, 2016 at 02:43:08PM -0600, Bjorn Helgaas wrote:
> > I saw responses from Keith and Bryan, and I hope they answer your
> > questions. As far as I can tell, the VMD driver is grossly similar to
> > other host bridge drivers we've already merged, and I don't think we
> > have public specs for all of them.
> >
> > Unless you have further concerns, I'm going to ask Linus to pull this
> > tomorrow, along with the rest of the PCI changes for v4.5.
>
> I still think it's a bad idea to merge something odd like this without
> a good explanation or showing what devices can actually sit under it.
>
> But you're the maintainer in the end..
Any PCIe devices and and bridges should work with existing upstream
drivers. The only exceptions would be anything depndent on INTx or IO
ports.
Powered by blists - more mailing lists