[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.
"Richard B. Johnson" wrote:
> What is its purpose? __SMP__ is not just defined or not defined from
> the linux kernel source directory, but also used for writing modules
> which, in fact, may not exist within the kernel source directory at
> all.
> 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".

__SMP__ has been obsolete ever since SMP was made a real config option.
This patch is just finishing the job. If a standalone module must
continue to use __SMP__, it could do:

#if defined(CONFIG_SMP) && !defined(__SMP__)
#define __SMP__

This has been discussed before. Change during a development kernel is
expected. Backwards compatability is not guaranteed. We don't want to
fall into that trap.


Brian Gerst

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.079 / U:1.724 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site