Date: Wed, 29 Apr 2015 12:06:22 -0400
From: Steven Rostedt <rostedt@goodmis.org>
To: Alex =?UTF-8?B?QmVubsOpZQ==?= <alex.bennee@linaro.org>
Cc: mingo@redhat.com, Dave.Martin@arm.com, linux-kernel@vger.kernel.org,
        Oleg Nesterov <oleg@redhat.com>, Javi Merino <javi.merino@arm.com>,
        "Peter Zijlstra \(Intel\)" <peterz@infradead.org>
Subject: Re: [PATCH v2] tracing: make ftrace_print_array_seq compute buf_len
Message-ID: <20150429120622.48c62110@gandalf.local.home>
In-Reply-To: <87mw1q2a8l.fsf@linaro.org>
References: <1430320727-14582-1-git-send-email-alex.bennee@linaro.org>
	<20150429113630.7595e9ce@gandalf.local.home>
	<87mw1q2a8l.fsf@linaro.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1260
Lines: 37

On Wed, 29 Apr 2015 17:02:50 +0100
Alex Bennée <alex.bennee@linaro.org> wrote:

> 
> Steven Rostedt <rostedt@goodmis.org> writes:
> 
> > On Wed, 29 Apr 2015 16:18:46 +0100
> > Alex Bennée <alex.bennee@linaro.org> wrote:
> >
> >> The only caller to this function (__print_array) was getting it wrong by
> >> passing the array length instead of buffer length. As the element size
> >> was already being passed for other reasons it seems reasonable to push
> >> the calculation of buffer length into the function.
> >> 
> >> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> >
> > Thanks, I'll add a stable tag to this too, and get it out soon.
> 
> I take it you'll pick up Dave's reviewed-by?

Yep, I will.

> 
> As for CC'ing stable I wouldn't worry too much as nothing in the kernel
> uses __print_array yet (unless you count the example). But it is a
> fairly trivial patch so if you as the maintainer is happy I'm happy ;-)

OK, if it's not used, then I'll just add it to this release.

Thanks,

-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/