linux-kernel - Re: [tip:perf/core] perf: Update perf_event

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: <alpine.DEB.2.02.1307250828510.18434@pianoman.cluster.toy>
Date:	Thu, 25 Jul 2013 08:31:34 -0400 (EDT)
From:	Vince Weaver <vince@...ter.net>
To:	Peter Zijlstra <peterz@...radead.org>
cc:	mingo@...nel.org, hpa@...or.com, linux-kernel@...r.kernel.org,
	adrian.hunter@...el.com, tglx@...utronix.de,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perf/core] perf: Update perf_event_type documentation

On Thu, 25 Jul 2013, Peter Zijlstra wrote:

> I didn't add any fields, this is simply catching up with what was
> already there. But yes, this is very much intended to be compatible.

So those id fields have been there since 2.6.31 and just no one noticed 
the header file comments were wrong?  That's fine then, I just have a lot 
of code and other documentation that needs to be updated then.

> I suppose you're 'complaining' about these changes? Yeah, maybe I should
> have split them up in a separate patch.
>
> ...
> 
> It should be a NOP functionality wise.

yes, it looks like a NOP.  I was just surprised to see code changes (even 
trivial ones) when the commit message only said documentation update.

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