Re: 3.19: device name associates with IRQ's for ahci controllers operating with a single IRQ changed from "ahci?" to "<BDF>"

From: Alexander Gordeev <agordeev@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: Stefan Bader <stefan.bader@canonical.com>,
	Sander Eikelenboom <linux@eikelenboom.it>,
	linux-kernel@vger.kernel.org
Subject: Re: 3.19: device name associates with IRQ's for ahci controllers operating with a single IRQ changed from "ahci?" to "<BDF>"
Date: Thu, 12 Feb 2015 16:33:53 +0000	[thread overview]
Message-ID: <20150212163352.GB23101@agordeev.usersys.redhat.com> (raw)
In-Reply-To: <20150210145120.GI3220@htj.duckdns.org>

On Tue, Feb 10, 2015 at 09:51:20AM -0500, Tejun Heo wrote:
> Hello,
> 
> On Tue, Feb 10, 2015 at 08:57:46AM +0100, Stefan Bader wrote:
> > On 09.02.2015 20:54, Sander Eikelenboom wrote:
> > > Hi.
> > > 
> > > In 3.19 the device name associates with IRQ's for ahci controllers operating
> > > with a single IRQ changed from "ahci?" to "<BDF>", was this intentional ?
> > > 
> > > It's probably commit 18dcf433f3ded61eb140a55e7048ec2fef79e723 (or another one
> > > in that series). 
> > 
> > Oh, looking at that commit that might make sense. In
> > ahci_host_activate_single_irq it now uses dev_driver_name instead of dev_name as
> > it did before (from ata_host_activate).  The description sounds like before the
> > driver is registered this will return the bus. And registering an interrupt
> > would likely be before the driver is fully registered... But you probably saw
> > that, too. Whether that really was intentional is still the question. :)
> 
> Urgh... Alexander, can you please send a patch to fix up the names?

Will try to send over the weekend.

> Thanks.
> 
> -- 
> tejun

-- 
Regards,
Alexander Gordeev
agordeev@redhat.com