Re: [PATCH 0/1] ring-buffer fix for 2.6.28

[Steven Rostedt]

On Wed, 26 Nov 2008, Randy Dunlap wrote:

> 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.
> 

It's my scripts that post. I should probably modify it so that if there is 
only one patch, that I append it to the prolog instead, and mail it out 
the old way. My scripts pull the patches out of my git tree and use quilt 
top post. I know git has a way to do that too, but I have not set that up.

-- Steve

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