public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Lai Jiangshan <laijs@cn.fujitsu.com>
Subject: Re: [PATCH 0/1] ring-buffer fix for 2.6.28
Date: Wed, 26 Nov 2008 19:11:14 -0800	[thread overview]
Message-ID: <492E0FD2.8040805@oracle.com> (raw)
In-Reply-To: <20081127025227.026028481@goodmis.org>

Steven Rostedt wrote:
> The following patch needs to go into 2.6.28. It protects against
> a recursion race that can happen when the scheduler is traced.
> 
> The following patches are in:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> 
>     branch: devel
> 
> 
> Lai Jiangshan (1):
>       ring-buffer: prevent recursion
> 
> ----
>  kernel/trace/ring_buffer.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)

Is there something about git that causes (or forces) the use of
patch 0/1 followed by patch 1/1?  I find it terribly unwanted.

thanks,
-- 
~Randy

  parent reply	other threads:[~2008-11-27  3:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-27  2:52 [PATCH 0/1] ring-buffer fix for 2.6.28 Steven Rostedt
2008-11-27  2:52 ` [PATCH 1/1] ring-buffer: prevent recursion Steven Rostedt
2008-11-27  3:11 ` Randy Dunlap [this message]
2008-11-27 13:58   ` [PATCH 0/1] ring-buffer fix for 2.6.28 Steven Rostedt
2008-11-27  9:14 ` Ingo Molnar

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=492E0FD2.8040805@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.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