[lkml]   [2000]   [Jan]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] Replacing __SMP__ by CONFIG_SMP globally in linux-2.3.39.
Niels Kristian Bech Jensen wrote:

>> > So, if such a patch goes into the kernel, module makefiles now have
>> > to be modified to define "CONFIG_SMP" instead of "__SMP__" which,
>> > since they may not even have a "configuration", becomes just another
>> > PITA to support "change for the sake of change".
>> >
>> The purpose is to get rid of what I consider an ugly hack. Since
>> CONFIG_SMP is a proper config option, it and only it should be used IMHO.
>> What is the purpose of having a config option symbol (CONFIG_SMP) define
>> another symbol (__SMP__) ?

> The first to define a symbol makes the rule. How do you claim that
> "CONFIG_SMP" is any more `proper` than "__SMP__" ?

For one, the build-dependency system of the kernel can handle CONFIG_SMP.

Arjan van de Ven

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

 \ /
  Last update: 2005-03-22 13:55    [W:0.059 / U:11.940 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site