From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Tseng-Hui (Frank) Lin" <thlin@linux.vnet.ibm.com>
Cc: tsenglin@us.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 3/3] powerpc: Add IO event interrupt support
Date: Tue, 08 Feb 2011 08:46:20 +1100 [thread overview]
Message-ID: <1297115180.14982.83.camel@pasglop> (raw)
In-Reply-To: <1297114832.24377.42.camel@flin.austin.ibm.com>
On Mon, 2011-02-07 at 15:40 -0600, Tseng-Hui (Frank) Lin wrote:
> > We are -really- re-inventing interrupts and/or notifiers here, which
> > I find a tad annoying..
>
> Agree. This is ugly. We could have just used the regular interrupt
> mechanism if the firmware didn't use shared rtas call and interrupt
> to report multiple types of events.
A notifier wouldn't have worked ?
Cheers,
Ben.
next prev parent reply other threads:[~2011-02-07 21:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 22:44 [PATCH v2 3/3] powerpc: Add IO event interrupt support Tseng-Hui (Frank) Lin
2011-02-07 5:10 ` Benjamin Herrenschmidt
2011-02-07 21:40 ` Tseng-Hui (Frank) Lin
2011-02-07 21:46 ` Benjamin Herrenschmidt [this message]
2011-02-08 14:29 ` Tseng-Hui (Frank) Lin
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=1297115180.14982.83.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=thlin@linux.vnet.ibm.com \
--cc=tsenglin@us.ibm.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).