linux-kernel - Re: [PATCH] perf report: Fix some option handling on --stdio

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, 14 May 2015 17:06:34 +0900
From:	Namhyung Kim <namhyung@...nel.org>
To:	Arnaldo Carvalho de Melo <acme@...nel.org>
Cc:	Ingo Molnar <mingo@...nel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Jiri Olsa <jolsa@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	David Ahern <dsahern@...il.com>,
	Taeung Song <treeze.taeung@...il.com>
Subject: Re: [PATCH] perf report: Fix some option handling on --stdio

Hi Arnaldo,

On Wed, May 13, 2015 at 01:07:19PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, May 14, 2015 at 12:03:26AM +0900, Namhyung Kim escreveu:
> > There's a bug that perf report sometimes ignore some options on --stdio
> > output.  This bug is triggered only if a related config variable is
> > set.  For example, let's assume we have a following config file.
> 
> Testing, please next time indicate against what branch this is to be
> applied, as I thought about perf/core, but it doesn't apply there, so
> tried perf/urgent, where it applies.

Oh, sorry about that.  I actually intended to apply it to the
perf/core but forgot to rebase to the current code.  It's fortunate
that it can be applied to perf/urgent cleanly though. :)

I'll add an indication next time if patch should go to other branch
than perf/core.

Thanks,
Namhyung
--
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/