[lkml]   [2007]   [Mar]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Why is arch/s390/crypto/Kconfig sourced when building for another arch ?
On Fri, 2007-03-30 at 05:55 -0400, Robert P. J. Day wrote:
> i'm betting the S390 folks would *really* hate that idea but, if you
> look closely, the generic Kconfig file *already* has some
> arch-dependent content:
> ...
> tristate "Support for VIA PadLock ACE"
> depends on X86_32 <-----
> ...

Yes, but the padlock driver is located under drivers/crypto. The s390
crypto stuff is not. It is under arch/s390/crypto, thats why the Kconfig
file is there...

Both solutions (the current and your proposed) are somehow ugly.
I don't care too much, where the Kconfig entries are, as long as it
works. So if you're interested in changing it go forward and post a


> i think it's a matter of deciding how to be consistent. either you
> allow individual architectures to define their own additional Kconfig
> files or you don't. mixing the two approaches is a recipe for
> confusion.
> rday

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-03-30 18:23    [W:0.045 / U:2.076 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site