public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/2] ring-buffer: updates for 2.6.28
Date: Tue, 23 Dec 2008 18:46:53 +0100	[thread overview]
Message-ID: <20081223174653.GA21738@elte.hu> (raw)
In-Reply-To: <20081223163223.625941559@goodmis.org>


* Steven Rostedt <rostedt@goodmis.org> wrote:

> Ingo,
> 
> These two patches should go to 2.6.28. They are fixes to the ring buffer 
> for bugs that will make the ring buffer stop reading, and/or produce a 
> false positive.
> 
> If these are too late for 2.6.28, then we probably should get them at 
> least to the stable branch and queued for 2.6.28.1.

yes, they are too late - the .28 release is tomorrow.

> Steven Rostedt (2):
>       ring-buffer: fix dangling commit race
>       ring-buffer: prevent false positive warning
> 
> ----
>  kernel/trace/ring_buffer.c |   19 +++++++++++++++++--
>  1 files changed, 17 insertions(+), 2 deletions(-)

pulled into tip/tracing/ring-buffer. I also marked them Cc: 
stable@kernel.org, so they will be picked up for .28.1. (they apply 
cleanly to both the latest tracing tree and latest mainline as well)

	Ingo

      parent reply	other threads:[~2008-12-23 17:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-23 16:32 [PATCH 0/2] ring-buffer: updates for 2.6.28 Steven Rostedt
2008-12-23 16:32 ` [PATCH 1/2] ring-buffer: fix dangling commit race Steven Rostedt
2008-12-23 16:32 ` [PATCH 2/2] ring-buffer: prevent false positive warning Steven Rostedt
2008-12-23 16:40 ` [PATCH 0/2] ring-buffer: updates for 2.6.28 Steven Rostedt
2008-12-23 17:46 ` Ingo Molnar [this message]

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=20081223174653.GA21738@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --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