On Sat, 08 Dec 2007 10:32:57 -0500 Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
> @@ -21,7 +21,7 @@ config PROFILING
> config OPROFILE
> tristate "OProfile system profiling (EXPERIMENTAL)"
> depends on PROFILING && !UML
> - depends on ALPHA || ARM || AVR32 || BLACKFIN || X86_32 ||
Linus:
On the per-architecture side, I do think it would be better to *not* have
internal architecture knowledge in a generic file, and as such a line like
depends on X86_32 || IA64 || PPC || S390 || SPARC64 || X86_64 || AVR32
really shouldn't exist in a file like kernel/Kconfig.instrumen
Linus:
On the per-architecture side, I do think it would be better to *not* have
internal architecture knowledge in a generic file, and as such a line like
depends on X86_32 || IA64 || PPC || S390 || SPARC64 || X86_64 || AVR32
really shouldn't exist in a file like kernel/Kconfig.instrumen
On Thu, 15 Nov 2007 22:30:59 -0500
Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
> Linus:
> On the per-architecture side, I do think it would be better to *not* have
> internal architecture knowledge in a generic file, and as such a line like
>
> depends on X86_32 || IA64 || PPC || S390 ||
Linus:
On the per-architecture side, I do think it would be better to *not* have
internal architecture knowledge in a generic file, and as such a line like
depends on X86_32 || IA64 || PPC || S390 || SPARC64 || X86_64 || AVR32
really shouldn't exist in a file like kernel/Kconfig.instrumen
5 matches
Mail list logo