From: Andi Kleen <ak@suse.de>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>,
torvalds <torvalds@osdl.org>
Subject: Re: [PATCH 0/9] Replace some ARCH_HAS_XYZZY
Date: Tue, 8 Aug 2006 05:15:10 +0200 [thread overview]
Message-ID: <200608080515.10496.ak@suse.de> (raw)
In-Reply-To: <20060807200804.7847e6d0.rdunlap@xenotime.net>
> They are config characteristics (in many cases). Hiding them in
> header files with dummy inlines or with ARCH_HAS_XYZZY is still
> hiding them IMO, although the inlines are better than the
> ARCH_HAS_XYZZY method. I prefer to see them in the config space
> since I think that's where they belong.
That's just a different way to write a #define. You could as
well keep the originals then.
-Andi
next prev parent reply other threads:[~2006-08-08 3:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 21:13 [PATCH 0/9] Replace some ARCH_HAS_XYZZY Randy.Dunlap
2006-08-08 2:05 ` Andi Kleen
2006-08-08 3:08 ` Randy.Dunlap
2006-08-08 3:15 ` Andi Kleen [this message]
2006-08-08 4:27 ` Randy.Dunlap
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=200608080515.10496.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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