From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH] [2.6.22] powerpc: uninline and export virq_to_hw()
Date: Mon, 04 Jun 2007 15:27:21 +1000 [thread overview]
Message-ID: <1180934841.31677.42.camel@localhost.localdomain> (raw)
In-Reply-To: <20070604052707.GA27896@lixom.net>
On Mon, 2007-06-04 at 00:27 -0500, Olof Johansson wrote:
>
> > It's called in fairly hot IRQ code path (the PIC themselves use it)
> no ?
>
> I looked before I did the change. All of those open-code it.
Ah ok :-) Yeah, well, I remember open coding it when I wrote the PIC
code for virq's then somebody added virq_to_hw() :-)
Good to go then,
Cheers,
Ben.
prev parent reply other threads:[~2007-06-04 5:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 4:47 [PATCH] [2.6.22] powerpc: uninline and export virq_to_hw() Olof Johansson
2007-06-04 5:20 ` Benjamin Herrenschmidt
2007-06-04 5:27 ` Olof Johansson
2007-06-04 5:27 ` Benjamin Herrenschmidt [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=1180934841.31677.42.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--cc=paulus@samba.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).