All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: John Kacur <jkacur@gmail.com>, Roland McGrath <roland@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] ptrace: kill BKL in ptrace syscall
Date: Thu, 1 Apr 2010 20:48:58 +0200	[thread overview]
Message-ID: <20100401184855.GB6142@nowhere> (raw)
In-Reply-To: <20100329183502.GA17842@redhat.com>

On Mon, Mar 29, 2010 at 08:35:02PM +0200, Oleg Nesterov wrote:
> On 03/29, Frederic Weisbecker wrote:
> >
> > On Mon, Mar 29, 2010 at 03:26:26PM +0200, John Kacur wrote:
> > > On Mon, Mar 29, 2010 at 3:05 PM, Oleg Nesterov <oleg@redhat.com> wrote:
> > > >
> > > > Cough. I must admit, apart from "urgent" bugfixes the only way I know
> > > > is to send the patch to Andrew.
> > > >
> > > > So I'd suggest to send this patch to akpm. Of course, if you wish I can
> > > > forward it, but doesn't matter.
> > > >
> > > I know that in the past, Thomas was keeping a BKL tree in tip, but not sure if
> > > he is still doing so. It seems that Arnd's tree is at least partially
> > > experimental,
> > > so I wonder if we need to maintain another BKL tree somewhere of fixes
> > > that have no
> > > obvious maintainer, but are ready to send to Linus for inclusion?
> >
> >
> > I have cc'ed Andrew for this patch, partly for that purpose, so that he
> > can take it if he wants to.
> 
> Ah, good, I didn't notice.
> 
> If he doesn't pick this patch now, I'll forward it to him later again ;)
> 
> > But in the worst case these patches are never lost. We don't want to lose
> > them. For those that can't go in someone else .35 targeted tree for any reason,
> > I can queue them up in mine in a dedicated branch that I'll propose to Linus.
> 
> Frederic, whatever is more convenient to you.
> 
> Oleg.
> 


I have applied it to:

git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
	bkl/core

Thanks.


  parent reply	other threads:[~2010-04-01 17:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-28 21:38 [PATCH] ptrace: kill BKL in ptrace syscall Frederic Weisbecker
2010-03-28 21:45 ` Frederic Weisbecker
2010-03-29 11:40 ` Oleg Nesterov
2010-03-29 12:06   ` John Kacur
2010-03-29 13:05     ` Oleg Nesterov
2010-03-29 13:26       ` John Kacur
2010-03-29 18:22         ` Frederic Weisbecker
2010-03-29 18:35           ` Oleg Nesterov
2010-03-29 18:46             ` Frederic Weisbecker
2010-04-01 18:48             ` Frederic Weisbecker [this message]
2010-04-12 20:29               ` Andrew Morton
2010-04-12 20:32                 ` Frederic Weisbecker
2010-04-12 23:56                 ` Stephen Rothwell
2010-04-09 21:43   ` Roland McGrath

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=20100401184855.GB6142@nowhere \
    --to=fweisbec@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=jkacur@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=roland@redhat.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.