From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, Felipe Damasio <felipewd@terra.com.br>
Subject: Re: [PATCH] 8139cp: Catch all interrupts
Date: Mon, 31 Oct 2005 19:14:44 +0100 [thread overview]
Message-ID: <43665F14.9040700@drzeus.cx> (raw)
In-Reply-To: <431761BA.5080007@drzeus.cx>
Pierre Ossman wrote:
> Register interrupt handler when net device is registered. Avoids missing
> interrupts if the interrupt mask gets out of sync.
>
> Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
>
> ---
>
> The reason this patch is needed for me is that the resume function is
> broken. It enables interrupts unconditionally, but the interrupt handler
> is only registered when the device is up.
>
> I don't have enough knowledge about the driver to fix the resume
> function so this patch will instead make sure that the interrupt handler
> is registered at all times (which can be a nice safeguard even when the
> resume function gets fixed).
>
Any comments on this?
prev parent reply other threads:[~2005-10-31 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 20:16 [PATCH] 8139cp: Catch all interrupts Pierre Ossman
2005-10-31 18:14 ` Pierre Ossman [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=43665F14.9040700@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=felipewd@terra.com.br \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).