From: "stanley.miao" <stanley.miao@windriver.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Steve.Glendinning@smsc.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 18:22:50 +0800 [thread overview]
Message-ID: <1231928570.6810.12.camel@localhost> (raw)
In-Reply-To: <20090114100550.GA22976@n2100.arm.linux.org.uk>
On Wed, 2009-01-14 at 10:05 +0000, Russell King - ARM Linux wrote:
> On Wed, Jan 14, 2009 at 08:54:36AM +0000, Steve.Glendinning@smsc.com wrote:
> > > When calling request IRQ it is desirable to allow platforms
> > > to specific flags for the call to request_irq. Adding irq_flags
> > > to smsc911x_platform_config allows these flags to be passed.
> > >
> > > Signed-off-by: Stanley.Miao <stanley.miao@windriver.com>
> >
> > Acked-by: Steve Glendinning <steve.glendinning@smsc.com>
> >
> > Thanks Stanley.
> >
> > 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?
>
> Does this really make sense? Normally, the interrupt level/edge stuff is
> passed through the resource structure.
>
> I can't really comment because it seems that there's no way to work out
> what patch you're acking. I can't find it in the last 6 months of email,
> and there's no attributation for your quoted reply to hint at when the
> original message was sent.
Hi, Russell,
Did you subscribe netdev mail list ? Maybe it was filtered into netdev
mail list. I just send the patch 4 hours ago.
Stanley.
next prev parent reply other threads:[~2009-01-14 10:14 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 [this message]
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
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=1231928570.6810.12.camel@localhost \
--to=stanley.miao@windriver.com \
--cc=Steve.Glendinning@smsc.com \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux@arm.linux.org.uk \
--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 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.