From: David Miller <davem@davemloft.net>
To: cascardo@linux.vnet.ibm.com
Cc: netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] ehea: only register irq after setting up ports
Date: Tue, 24 Apr 2012 00:37:07 -0400 (EDT) [thread overview]
Message-ID: <20120424.003707.1304020185354100560.davem@davemloft.net> (raw)
In-Reply-To: <1335188789-6211-1-git-send-email-cascardo@linux.vnet.ibm.com>
From: Thadeu Lima de Souza Cascardo <cascardo@linux.vnet.ibm.com>
Date: Mon, 23 Apr 2012 10:46:29 -0300
> If we receive an interrupt too early before we set up ports in the probe
> function, there won't be any port ready to handle it.
>
> Only registering the irq after the ports are setup fixes the problem,
> and works fine without losing any interrupts.
>
> This causes crashes in some situations:
...
> Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@linux.vnet.ibm.com>
> Cc: stable@vger.kernel.org
Applied, thanks for fixing this properly.
prev parent reply other threads:[~2012-04-24 4:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 13:46 [PATCH] ehea: only register irq after setting up ports Thadeu Lima de Souza Cascardo
2012-04-24 4:37 ` 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=20120424.003707.1304020185354100560.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cascardo@linux.vnet.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=stable@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).