[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTinNUnq7JQDpTzCv24A7T7fMn9iPFisQEBZGkELr@mail.gmail.com>
Date: Tue, 22 Feb 2011 20:33:45 +0100
From: Ivo Van Doorn <ivdoorn@...il.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Ben Hutchings <bhutchings@...arflare.com>,
LKML <linux-kernel@...r.kernel.org>,
netdev <netdev@...r.kernel.org>, Felix Fietkau <nbd@...nwrt.org>,
"John W. Linville" <linville@...driver.com>, abogani@...ware.it
Subject: Re: [PATCH] rt2x00: Use ops name instead of device name
Hi,
On Tue, Feb 22, 2011 at 2:44 PM, Steven Rostedt <rostedt@...dmis.org> wrote:
> On Tue, 2011-02-22 at 13:34 +0000, Ben Hutchings wrote:
>
>> > 19: 73474106 0 IO-APIC-fasteoi ata_piix, uhci_hcd:usb6, 0000:05:01.0
>
>> > rt2x00dev->irq = pci_dev->irq;
>> > - rt2x00dev->name = pci_name(pci_dev);
>> > + rt2x00dev->name = ops->name;
>
>
>> But then how can users distinguish the IRQs for multiple devices handled
>> by the same driver? (Probably unusual for WLAN devices, but still
>> possible.)
>>
>> I assume you can't use a net device name as there may be multiple net
>> devices per bus device?
>
> Honestly, I do not know this code well enough, but this patch seemed to
> solve the problem at hand. Hence I sent it out to the experts hoping
> they either take this patch or come up with a proper solution ;)
>
> In any case, just posting the pci address is not a pretty answer.
I just checked the other wireless drivers, and they all seem to use
the modulename. So I guess your patch is correct. You can add my:
Acked-by: Ivo van Doorn <IvDoorn@...il.com>
--
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/
Powered by blists - more mailing lists