linux-kernel - Re: [PATCH tip 1/2] ring_buffer: remove unused flags parameter

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: <20090206000223.GB16040@elte.hu>
Date:	Fri, 6 Feb 2009 01:02:23 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Arnaldo Carvalho de Melo <acme@...hat.com>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	Frédéric Weisbecker <fweisbec@...il.com>,
	Jens Axboe <jens.axboe@...cle.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH tip 1/2] ring_buffer: remove unused flags parameter


* Arnaldo Carvalho de Melo <acme@...hat.com> wrote:

> Impact: API change, cleanup
> 
> >From ring_buffer_{lock_reserve,unlock_commit}.
> 
> Cc: Ingo Molnar <mingo@...e.hu>
> Cc: Frédéric Weisbecker <fweisbec@...il.com>
> Cc: Jens Axboe <jens.axboe@...cle.com>
> Signed-off-by: Arnaldo Carvalho de Melo <acme@...hat.com>
> ---
>  block/blktrace.c                 |    8 +++---
>  include/linux/ring_buffer.h      |    9 ++----
>  kernel/trace/kmemtrace.c         |   12 +++-----
>  kernel/trace/ring_buffer.c       |    9 +-----
>  kernel/trace/trace.c             |   56 +++++++++++++------------------------
>  kernel/trace/trace_boot.c        |   12 +++-----
>  kernel/trace/trace_branch.c      |    7 ++---
>  kernel/trace/trace_hw_branches.c |    6 ++--
>  kernel/trace/trace_mmiotrace.c   |   12 +++-----
>  kernel/trace/trace_power.c       |   12 +++-----
>  10 files changed, 51 insertions(+), 92 deletions(-)

Applied to tip:tracing/ftrace, thanks Arnaldo!

	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/