linux-kernel - Re: [PATCH 04/11] perf tools: Move debugfs__strerror

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: <20150828125909.GD2759@codeblueprint.co.uk>
Date:	Fri, 28 Aug 2015 13:59:09 +0100
From:	Matt Fleming <matt@...eblueprint.co.uk>
To:	Jiri Olsa <jolsa@...nel.org>
Cc:	Arnaldo Carvalho de Melo <acme@...nel.org>,
	lkml <linux-kernel@...r.kernel.org>,
	David Ahern <dsahern@...il.com>,
	Ingo Molnar <mingo@...nel.org>,
	Namhyung Kim <namhyung@...nel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Raphaël Beamonte <raphael.beamonte@...il.com>
Subject: Re: [PATCH 04/11] perf tools: Move debugfs__strerror_open into
 util.c object

On Wed, 26 Aug, at 03:46:46PM, Jiri Olsa wrote:
> Moving debugfs__strerror_open out of api/fs/debugfs.c,
> because it's not debugfs specific. It'll be changed to
> consider tracefs mount as well in following patches.
> 
> Link: http://lkml.kernel.org/n/tip-bq0f0l4r0bjvy0pjp4m759kv@git.kernel.org
> Signed-off-by: Jiri Olsa <jolsa@...nel.org>
> ---
>  tools/lib/api/fs/debugfs.c | 51 ---------------------------------------------
>  tools/lib/api/fs/debugfs.h |  3 ---
>  tools/perf/util/util.c     | 52 ++++++++++++++++++++++++++++++++++++++++++++++
>  tools/perf/util/util.h     |  2 ++
>  4 files changed, 54 insertions(+), 54 deletions(-)

Reviewed-by: Matt Fleming <matt.fleming@...el.com>

-- 
Matt Fleming, Intel Open Source Technology Center
--
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/