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:	Thu, 7 May 2009 11:04:36 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Christoph Hellwig <hch@....de>, rostedt@...dmis.org,
	linux-kernel@...r.kernel.org,
	Fr?d?ric Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH] sh: remove stray markers

On Wed, May 06, 2009 at 01:15:49PM +0200, Ingo Molnar wrote:
> 
> * Christoph Hellwig <hch@....de> wrote:
> 
> > On Wed, May 06, 2009 at 01:07:35PM +0200, Ingo Molnar wrote:
> > > 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.
> > 
> > There's not user of these. [...]
> 
> I'll defer to Paul to decide whether SH needs those markers. If he 
> added them to ease his own debugging (via whatever external 
> approach), then that's an OK goal and we can handle this all 
> politely without destroying functionality, in the next merge window.
> 
They were primarily added to aid some downstream folks that were just
adding these on their own and generally not paying attention to where the
markers were being placed on subsequent merges. I don't feel too strongly
one way or the other, but as they have proven to be useful for some
people, I would rather transition over to tracepoints during the merge
window than kill them off prematurely.
--
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/