From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: cmetcalf@tilera.com, shemminger@vyatta.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] marvell sky2 driver: fix irq number assignment bug
Date: Tue, 03 Apr 2012 17:41:39 -0400 (EDT) [thread overview]
Message-ID: <20120403.174139.1088270699067881012.davem@davemloft.net> (raw)
In-Reply-To: <1333468024.2577.21.camel@bwh-desktop.uk.solarflarecom.com>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Tue, 3 Apr 2012 16:47:04 +0100
> On Tue, 2012-04-03 at 11:10 -0400, Chris Metcalf wrote:
>> Fix a minor bug that will display wrong IRQ number in ifconfig output.
>>
>> Signed-off-by: Chris Metcalf <cmetcalf@tilera.com>
>> ---
>> drivers/net/ethernet/marvell/sky2.c | 7 +++++++
>> 1 files changed, 7 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/marvell/sky2.c b/drivers/net/ethernet/marvell/sky2.c
>> index 423a1a2..879b0a4 100644
>> --- a/drivers/net/ethernet/marvell/sky2.c
>> +++ b/drivers/net/ethernet/marvell/sky2.c
>> @@ -4978,6 +4978,13 @@ static int __devinit sky2_probe(struct pci_dev *pdev,
>> goto err_out_free_netdev;
>> }
>>
>> + /*
>> + * Need to set the IRQ # for the net_device here again after
>> + * setting it in sky2_init_netdev() initially, because MSI
>> + * will assign a new IRQ # to this PCI device.
>> + */
>> + dev->irq = hw->pdev->irq;
>> +
>> err = register_netdev(dev);
>> if (err) {
>> dev_err(&pdev->dev, "cannot register net device\n");
>
> I think the consensus now is that net_device::irq should be left at 0
> for devices that don't support manual configuration (ISA and the like).
Agreed.
prev parent reply other threads:[~2012-04-03 21:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 15:10 [PATCH] marvell sky2 driver: fix irq number assignment bug Chris Metcalf
2012-04-03 15:47 ` Ben Hutchings
2012-04-03 21:41 ` David Miller [this message]
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=20120403.174139.1088270699067881012.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=cmetcalf@tilera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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