linux-kernel - Re: [PATCH -tip] fix compilation error

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <495AC45D.8010102@kernel.org>
Date:	Tue, 30 Dec 2008 17:01:17 -0800
From:	"H. Peter Anvin" <hpa@...nel.org>
To:	Frederic Weisbecker <fweisbec@...il.com>
CC:	Jaswinder Singh Rajput <jaswinder@...radead.org>,
	Ingo Molnar <mingo@...e.hu>, x86 maintainers <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH -tip] fix compilation error

Frederic Weisbecker wrote:
> On Tue, Dec 30, 2008 at 04:34:00PM -0800, H. Peter Anvin wrote:
>> H. Peter Anvin wrote:
>>> Applied to tip:tracing/kmemtrace2.
>>>
>> Hm, there still seems to be a build failure, in particular
>> trace_output.h is missing.  It looks to me at the moment as if just
>> removing the #include works; assuming that compiles I will check that in
>> to tip:tracing/kmemtrace2 as well.
>>
>> 	-hpa
> 
> While I worked on this tracer, I had to base the thing against tracing/kmemtrace
> because I needed the kmemtrace bits.
> But I saw that this topic was a bit out of sync against tip/master, some updates from
> Steven were not merged. But I didn't wonder, thinking that Ingo would resolve the
> conflicts. But it seems there were some lost stuffs :-)
> 
> I'm checking it and will send a patch to solve the rest...
> 

If it's only the trace_output.h #include removal, don't worry about it;
I'm about to commit that patch, but it would be good if you could check
out the tracing/kmemtrace2 branch afterwards.

	-hpa
--
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/