public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 00/11] Text Edit Lock for 2.6.23-rc6-mm1
Date: Fri, 21 Sep 2007 18:29:50 +0100	[thread overview]
Message-ID: <20070921172950.GA22972@infradead.org> (raw)
In-Reply-To: <20070920161018.0b4e7ec3.akpm@linux-foundation.org>

On Thu, Sep 20, 2007 at 04:10:18PM -0700, Andrew Morton wrote:
> On Tue, 18 Sep 2007 17:06:01 -0400
> Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> wrote:
> 
> > Here are the text edit lock patches ported to 2.6.23-rc6-mm1.
> 
> I think I'll duck these one more time.  There was a bit of followup
> and for now I'd prefer to concentrate on obviously-safe stuff and
> stabilisation of the current 2.6.24 queue.

As much as I'd love to see markers as soon as possible I have to agree.

I really hate how the first post of a handfull easy patches touching
almost no core code has turned into this gigantic series.

Matthew, any chance you could resurrect a trivial, no-optimizations
marker variant that has so little impact it could go into 2.6.24?

I'd really love to have the infrastructure there so we can add optimizations
in parallel with actually adding the users to the tree.

  reply	other threads:[~2007-09-21 17:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-18 21:06 [patch 00/11] Text Edit Lock for 2.6.23-rc6-mm1 Mathieu Desnoyers
2007-09-18 21:06 ` [patch 01/11] Kprobes - use a mutex to protect the instruction pages list Mathieu Desnoyers
2007-09-18 21:06 ` [patch 02/11] Kprobes - do not use kprobes mutex in arch code Mathieu Desnoyers
2007-09-18 21:06 ` [patch 03/11] Kprobes - declare kprobe_mutex static Mathieu Desnoyers
2007-09-18 21:06 ` [patch 04/11] Add INIT_ARRAY() to kernel.h Mathieu Desnoyers
2007-09-18 21:06 ` [patch 05/11] Text Edit Lock - Architecture Independent Code Mathieu Desnoyers
2007-09-18 21:06 ` [patch 06/11] Text Edit Lock - Alternative code for i386 and x86_64 Mathieu Desnoyers
2007-09-18 21:06 ` [patch 07/11] Text Edit Lock - kprobes architecture independent support Mathieu Desnoyers
2007-09-18 21:06 ` [patch 08/11] Text Edit Lock - kprobes i386 Mathieu Desnoyers
2007-09-18 21:06 ` [patch 09/11] Text Edit Lock - kprobes x86_64 Mathieu Desnoyers
2007-09-18 21:06 ` [patch 10/11] Text Edit Lock - i386 standardize debug rodata Mathieu Desnoyers
2007-09-18 21:06 ` [patch 11/11] Text Edit Lock - x86_64 " Mathieu Desnoyers
2007-09-20 23:10 ` [patch 00/11] Text Edit Lock for 2.6.23-rc6-mm1 Andrew Morton
2007-09-21 17:29   ` Christoph Hellwig [this message]
2007-09-21 18:11     ` Mathieu Desnoyers

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=20070921172950.GA22972@infradead.org \
    --to=hch@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    /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