public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Werner Almesberger <werner@almesberger.net>
To: David Howells <dhowells@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	Rajesh Venkatasubramanian <vrajesh@umich.edu>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 3/3] prio_tree: move general code from mm/ to lib/
Date: Fri, 17 Dec 2004 20:16:44 -0300	[thread overview]
Message-ID: <20041217201644.F31842@almesberger.net> (raw)
In-Reply-To: <3700.1103325015@redhat.com>; from dhowells@redhat.com on Fri, Dec 17, 2004 at 11:10:15PM +0000

David Howells wrote:
> The prio_tree stuff can go back in for the nommu stuff. I've given Andrew a
> patch to that effect (copied to LKML).

Ah, found it. Great, so there should be no conflict anymore.

Thanks,
- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina     werner@almesberger.net /
/_http://www.almesberger.net/____________________________________________/

  reply	other threads:[~2004-12-17 23:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-17 18:36 [PATCH 0/3] prio_tree generalization Werner Almesberger
2004-12-17 18:37 ` [PATCH 1/3] prio_tree: roll call to prio_tree_first into prio_tree_next Werner Almesberger
2004-12-17 18:39 ` [PATCH 2/3] prio_tree: generalization Werner Almesberger
2004-12-17 18:40 ` [PATCH 3/3] prio_tree: move general code from mm/ to lib/ Werner Almesberger
2004-12-17 23:10   ` David Howells
2004-12-17 23:16     ` Werner Almesberger [this message]
2004-12-17 19:52 ` [PATCH 0/3] prio_tree generalization Andrew Morton

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=20041217201644.F31842@almesberger.net \
    --to=werner@almesberger.net \
    --cc=akpm@osdl.org \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vrajesh@umich.edu \
    /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