From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC] powerpc/irq: Add generic API for setting up cascaded IRQs
Date: Tue, 15 Sep 2009 20:02:38 +1000 [thread overview]
Message-ID: <1253008958.8375.213.camel@pasglop> (raw)
In-Reply-To: <fa686aa40909120705wdc8928ei75e9b8c952d1e45@mail.gmail.com>
> I'm a reverse polish kind of guy. I preferring 'subject'_'action'
> over 'action'_'subject' just because it groups like subjects together.
> But it doesn't matter much, especially in this case where 'subject'
> is in a group of exactly 1. :-)
>
> I'll do whichever you prefer.
I just caught myself calling something relocs_check instead of
check_relocs so I suppose it's fair game :-)
Whatever you want.
Cheers,
Ben.
next prev parent reply other threads:[~2009-09-15 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-12 5:46 [RFC] powerpc/irq: Add generic API for setting up cascaded IRQs Grant Likely
2009-09-12 6:28 ` Benjamin Herrenschmidt
2009-09-12 14:05 ` Grant Likely
2009-09-15 10:02 ` Benjamin Herrenschmidt [this message]
2009-09-15 11:04 ` Michael Ellerman
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=1253008958.8375.213.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@lists.ozlabs.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