linux-kernel - Re: [PATCH] sh: remove stray markers

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]

Date:	Wed, 6 May 2009 13:07:35 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Christoph Hellwig <hch@....de>
Cc:	rostedt@...dmis.org, lethal@...ux-sh.org,
	linux-kernel@...r.kernel.org,
	Frédéric Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH] sh: remove stray markers

* Christoph Hellwig <hch@....de> wrote:

> arch/sh has a couple of stray markers without any users introduced 
> in commit 3d58695edbfac785161bf282dc11fd42a483d6c9.  Remove them 
> in preparation of removing the markers in favour of the 
> TRACE_EVENT macro (and also because we don't keep dead code 
> around).
> 
> Paul, are you okay putting this in via the tracing tree?  I'd like 
> to have all marker removals queued up there so we can kill it in 
> one go once 2.6.31 opens.

It's fine with me to have this included in the SH tree as well. The 
process.c files tend to be frequently modified in architectures so 
having overlap between tip/tracing and the SH tree could become 
awkward to Paul.

Also, if there's some current use of these markers then it's OK to 
not do this change right now but replace them with tracepoints in 
the v2.6.31 merge window, after both the SH and the tracing 
infrastructure changes are upstream.

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