From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Lai Jiangshan <laijs@cn.fujitsu.com>
Subject: Re: [PATCH 0/2] git pull request for tip/tracing/urgent
Date: Tue, 10 Feb 2009 14:04:11 +0100 [thread overview]
Message-ID: <20090210130411.GB8341@elte.hu> (raw)
In-Reply-To: <20090209151744.459736868@goodmis.org>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> Ingo,
>
> Here's the changes by Lai. The bug scared me enough to investigate
> it further, to see if we had other bug reports that this could
> have fixed. But I found out that ring_buffer_read_page currently
> does not have any users. The only user I have is for my splice work,
> which has not been included yet.
>
> I guess Lai is adding one. These are true bug fixes to code that
> is in the kernel, even if that code is currently "dead code". But I think
> they should still be included in 29, since this will reflect on ftrace
> when we have developers starting to use it (such as Lai).
>
> The following patches are in:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
>
> branch: tip/tracing/urgent/devel
hm, the branch does not exist anymore:
fatal: Couldn't find remote ref tip/tracing/urgent/devel
fatal: Couldn't find remote ref tracing/urgent/devel
fatal: Couldn't find remote ref tracing/urgent
In any case, please include this in the devel path not the urgent path.
Urgent patches are for real regressions that occur with the upstream
kernel and affect users. New uses of tracing code should be done on
top of the tracing tree.
Ingo
next prev parent reply other threads:[~2009-02-10 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 15:17 Steven Rostedt
2009-02-09 15:17 ` [PATCH 1/2] ring_buffer: fix typing mistake Steven Rostedt
2009-02-09 15:17 ` [PATCH 2/2] ring_buffer: fix ring_buffer_read_page() Steven Rostedt
2009-02-09 15:22 ` [PATCH 0/2] git pull request for tip/tracing/urgent Steven Rostedt
2009-02-10 13:04 ` Ingo Molnar [this message]
2009-02-10 14:11 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090210130411.GB8341@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®