From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Steve.Glendinning@smsc.com
Cc: "Stanley.Miao" <stanley.miao@windriver.com>,
David Miller <davem@davemloft.net>,
linux-arm-kernel@lists.arm.linux.org.uk, netdev@vger.kernel.org
Subject: Re: [PATCHv2] smsc911x: add irq_flags in smsc911x_platform_config.
Date: Wed, 14 Jan 2009 10:19:46 +0000 [thread overview]
Message-ID: <20090114101946.GE22976@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <OF8C316D93.937F4899-ON8025753E.0030604F-8025753E.003106B3@smsc.com>
On Wed, Jan 14, 2009 at 08:54:36AM +0000, Steve.Glendinning@smsc.com wrote:
> I have two more arm platform smsc911x conversion patches (realview and
> pcm037) which I'll post for review shortly. Both also depend on this
> irq_flags change, as they register their interrupts shared. David: would
> it make sense to put this driver patch into the arm tree?
BTW, the shared-ness of an interrupt handler depends on how the interrupt
handler is written, not on whether you require the interrupt to be
exclusively owned or not.
So, if a driver is written to co-operate properly with shared interrupts
then it should always pass IRQF_SHARED.
next prev parent reply other threads:[~2009-01-14 10:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 6:58 [PATCHv2] smsc911x: add irq_flags in smsc911x_platform_config Stanley.Miao
2009-01-14 8:54 ` Steve.Glendinning
2009-01-14 9:30 ` David Miller
2009-01-14 9:52 ` Steve.Glendinning
2009-01-14 10:05 ` Russell King - ARM Linux
2009-01-14 10:11 ` Steve.Glendinning
2009-01-14 10:11 ` David Miller
2009-01-14 10:14 ` Russell King - ARM Linux
2009-01-14 10:22 ` stanley.miao
2009-01-14 10:17 ` Russell King - ARM Linux
2009-01-14 10:19 ` David Miller
2009-01-14 10:22 ` Russell King - ARM Linux
2009-01-14 10:19 ` Russell King - ARM Linux [this message]
2009-01-14 17:07 ` Russell King - ARM Linux
2009-01-15 2:45 ` stanley.miao
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=20090114101946.GE22976@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=Steve.Glendinning@smsc.com \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=stanley.miao@windriver.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;
as well as URLs for NNTP newsgroup(s).