From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: [Resend][PATCH] ACPI / glue: Drop .find_bridge() callback from struct acpi_bus_type Date: Thu, 28 Feb 2013 02:11:58 +0100 Message-ID: <1723405.gTrRpVTGu2@vostro.rjw.lan> References: <2612891.I2roH54cPk@vostro.rjw.lan> <20130227222032.GA28616@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7Bit Return-path: In-Reply-To: <20130227222032.GA28616@kroah.com> Sender: linux-ide-owner@vger.kernel.org To: Greg Kroah-Hartman Cc: ACPI Devel Maling List , LKML , Bjorn Helgaas , linux-usb@vger.kernel.org, Tejun Heo , linux-ide@vger.kernel.org, Jeff Garzik , Yinghai Lu List-Id: linux-acpi@vger.kernel.org On Wednesday, February 27, 2013 02:20:32 PM Greg Kroah-Hartman wrote: > On Wed, Feb 27, 2013 at 11:06:52PM +0100, Rafael J. Wysocki wrote: > > From: Rafael J. Wysocki > > > > After PCI has stopped using the .find_bridge() callback in > > struct acpi_bus_type, the only remaining users of it are SATA and > > USB. However, SATA only pretends to be a user, because it points > > that callback to a stub always returning -ENODEV, and USB uses it > > incorrectly, because as a result of the way it is used by USB every > > device in the system that doesn't have a bus type or parent is > > passed to usb_acpi_find_device() for inspection. > > > > What USB actually needs, though, is to call usb_acpi_find_device() > > for USB ports that don't have a bus type defined, but have > > usb_port_device_type as their device type. > > Ick, that's not good. Can you have the original creator of that code > (someone else from Intel, I can't remember at the moment), fix that up > properly and send me patches? That won't be necessary afer this patch. Or do you want to fix up USB separately first? Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center.