From: Keir Fraser <keir@xen.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>, Tim Deegan <tim@xen.org>
Cc: xen-devel@lists.xen.org
Subject: Re: 32bit xen and "claim"
Date: Mon, 05 Nov 2012 19:51:25 +0000 [thread overview]
Message-ID: <CCBDC93D.51044%keir@xen.org> (raw)
In-Reply-To: <0ea96cac-0b8f-43bc-99a9-d330b4ea3d76@default>
On 05/11/2012 19:00, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:
> #if !defined(CONFIG_X86)
>
> (why not #ifndef?)
We have no coding convention to prefer one over the other. Personally I
would say they are equally readable.
-- Keir
prev parent reply other threads:[~2012-11-05 19:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 20:34 32bit xen and "claim" Dan Magenheimer
2012-11-01 20:41 ` Jan Beulich
2012-11-01 20:55 ` Dan Magenheimer
2012-11-02 8:41 ` Jan Beulich
2012-11-05 19:16 ` Dan Magenheimer
2012-11-05 19:50 ` Keir Fraser
2012-11-06 9:44 ` Jan Beulich
2012-11-06 20:40 ` Dan Magenheimer
2012-11-07 8:25 ` Jan Beulich
2012-11-01 20:46 ` Tim Deegan
2012-11-01 20:57 ` Dan Magenheimer
2012-11-02 9:30 ` Tim Deegan
2012-11-05 19:00 ` Dan Magenheimer
2012-11-05 19:06 ` Tim Deegan
2012-11-05 19:51 ` Keir Fraser [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=CCBDC93D.51044%keir@xen.org \
--to=keir@xen.org \
--cc=dan.magenheimer@oracle.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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).