From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Trent Piepho <tpiepho@freescale.com>
Subject: Re: [PATCH] Introduce ppc_pci_flags accessors
Date: Thu, 11 Dec 2008 22:06:01 +1100 [thread overview]
Message-ID: <1228993561.22413.166.camel@pasglop> (raw)
In-Reply-To: <20081210195313.4014ca85@zod.rchland.ibm.com>
On Wed, 2008-12-10 at 19:53 -0500, Josh Boyer wrote:
>
> That's fine too. I think you can Michael can have a virtual
> arm-wrestling match to decide whether ppc_pci_has_flag or
> ppc_pci_flags_are_set wins ;)
I vote for _has_flag() :-)
I even wonder if we need the word "flag" in there at all, but then I'm
just being anal !
Cheers,
Ben.
prev parent reply other threads:[~2008-12-11 11:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 19:11 [PATCH] Introduce ppc_pci_flags accessors Josh Boyer
2008-12-10 23:46 ` Michael Ellerman
2008-12-10 23:54 ` Josh Boyer
2008-12-11 0:04 ` Michael Ellerman
2008-12-11 0:47 ` Josh Boyer
2008-12-11 0:17 ` Trent Piepho
2008-12-11 0:53 ` Josh Boyer
2008-12-11 11:06 ` 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=1228993561.22413.166.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=tpiepho@freescale.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).