[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Mon, 7 Aug 2006 21:27:22 -0700
From: "Randy.Dunlap" <rdunlap@...otime.net>
To: Andi Kleen <ak@...e.de>
Cc: lkml <linux-kernel@...r.kernel.org>, akpm <akpm@...l.org>,
torvalds <torvalds@...l.org>
Subject: Re: [PATCH 0/9] Replace some ARCH_HAS_XYZZY
On Tue, 8 Aug 2006 05:15:10 +0200 Andi Kleen wrote:
>
> > 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.
yes, except that
1. these aren't buried in random header files
2. these are in the kconfig system & namespace where they belong
---
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists