From: Andi Kleen <ak@suse.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andi Kleen <ak@suse.de>,
torvalds@osdl.org, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH 2/17] Generic backward compatibility includes for 4level
Date: Mon, 25 Oct 2004 19:02:16 +0200 [thread overview]
Message-ID: <20041025170216.GA9142@wotan.suse.de> (raw)
In-Reply-To: <1098723034.2798.35.camel@laptop.fenrus.org>
On Mon, Oct 25, 2004 at 06:50:34PM +0200, Arjan van de Ven wrote:
> > >
> > > Don't we normally add do { } while (0) after empty macros which look like
> > > a function?
> >
> > iirc Rusty tried to come up with an example some time ago where it actually
> > made a difference, but failed. But I can change it.
>
>
> if (foo)
> bar();
> else
> pml4_ERROR(x);
> something_else();
Doesn't make any difference. Try it. With a double else it may make
a difference, but that is extremly bad style imho and better resolved
with a {}. Also you'll get a clear compile error.
-Andi
prev parent reply other threads:[~2004-10-25 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 7:23 [PATCH 2/17] Generic backward compatibility includes for 4level Andreas Kleen
2004-10-25 9:39 ` Russell King
2004-10-25 16:06 ` Andi Kleen
2004-10-25 16:50 ` Arjan van de Ven
2004-10-25 17:02 ` Andi Kleen [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=20041025170216.GA9142@wotan.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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