From: Matthew Whitehead <tedheadster@gmail.com>
To: Nate Levesque <thenaterhood@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [net-next] Fix hardcoded interrupt name lp->name to use system device value
Date: Sun, 22 Sep 2013 22:25:33 -0400 [thread overview]
Message-ID: <20130923022532.GA17124@gmail.com> (raw)
In-Reply-To: <1379789381-3992-1-git-send-email-thenaterhood@gmail.com>
On Sat, Sep 21, 2013 at 06:49:41PM +0000, Nate Levesque wrote:
> The lance interrupt handler was using the hard-coded name which would make it difficult to tell where the interrupt came from. Changed to use the device name that made the interrupt.
>
> Signed-off-by: Nate Levesque <thenaterhood@gmail.com>
> ---
> drivers/net/ethernet/amd/lance.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/amd/lance.c b/drivers/net/ethernet/amd/lance.c
> index 5c72843..256f590 100644
> --- a/drivers/net/ethernet/amd/lance.c
> +++ b/drivers/net/ethernet/amd/lance.c
> @@ -754,7 +754,7 @@ lance_open(struct net_device *dev)
> int i;
>
> if (dev->irq == 0 ||
> - request_irq(dev->irq, lance_interrupt, 0, lp->name, dev)) {
> + request_irq(dev->irq, lance_interrupt, 0, dev->name, dev)) {
> return -EAGAIN;
> }
>
> --
> 1.8.1.2
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Reviewed-by: Matthew Whitehead <tedheadster@gmail.com>
next prev parent reply other threads:[~2013-09-23 2:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-21 18:49 [net-next] Fix hardcoded interrupt name lp->name to use system device value Nate Levesque
2013-09-23 2:25 ` Matthew Whitehead [this message]
2013-09-27 21:40 ` David Miller
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=20130923022532.GA17124@gmail.com \
--to=tedheadster@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=thenaterhood@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.