From: Tejun Heo <tj@kernel.org>
To: Stefan Bader <stefan.bader@canonical.com>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
Alexander Gordeev <agordeev@redhat.com>,
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: Tue, 10 Feb 2015 09:51:20 -0500 [thread overview]
Message-ID: <20150210145120.GI3220@htj.duckdns.org> (raw)
In-Reply-To: <54D9B9FA.9030900@canonical.com>
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?
Thanks.
--
tejun
next prev parent reply other threads:[~2015-02-10 14:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 19:54 3.19: device name associates with IRQ's for ahci controllers operating with a single IRQ changed from "ahci?" to "<BDF>" Sander Eikelenboom
2015-02-10 7:57 ` Stefan Bader
2015-02-10 14:51 ` Tejun Heo [this message]
2015-02-12 16:33 ` Alexander Gordeev
2015-02-16 17:28 ` Alexander Gordeev
2015-03-02 17:21 ` Tejun Heo
2015-03-02 18:58 ` Alexander Gordeev
2015-03-02 19:10 ` Tejun Heo
2015-03-02 19:20 ` Tejun Heo
2015-03-02 19:11 ` Sander Eikelenboom
2015-03-02 19:12 ` Tejun Heo
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=20150210145120.GI3220@htj.duckdns.org \
--to=tj@kernel.org \
--cc=agordeev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@eikelenboom.it \
--cc=stefan.bader@canonical.com \
/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