lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 23 Oct 2008 13:12:12 -0400 (EDT) From: Steven Rostedt <rostedt@...dmis.org> To: Frédéric Weisbecker <fweisbec@...il.com> cc: Ingo Molnar <mingo@...e.hu>, Alexey Dobriyan <adobriyan@...il.com>, Geert Uytterhoeven <geert@...ux-m68k.org>, Stephen Rothwell <sfr@...b.auug.org.au>, linux-next@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] tracing: fix a build error on alpha and m68k On Thu, 23 Oct 2008, Fr?d?ric Weisbecker wrote: > > But to let the core trace.c to be built for other types of tracing, > the best thing I see is to put some ifdef CONFIG_TRACE_IRQFLAGS on the > tracing_cpumask functions and structure, and actually on the creation > of this file. Is there a reason that you use "raw_local_irq_disable" instead of local_irq_disable? -- Steve -- 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