From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Hugh Dickins <hugh@veritas.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
William Lee Irwin III <wli@holomorphy.com>,
Rik van Riel <riel@redhat.com>, Andrew Morton <akpm@osdl.org>,
Rajesh Venkatasubramanian <vrajesh@umich.edu>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rmap 18 i_mmap_nonlinear
Date: Thu, 29 Apr 2004 16:20:20 +0100 [thread overview]
Message-ID: <20040429162020.J16407@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0404291516380.5661-100000@localhost.localdomain>; from hugh@veritas.com on Thu, Apr 29, 2004 at 03:24:03PM +0100
On Thu, Apr 29, 2004 at 03:24:03PM +0100, Hugh Dickins wrote:
> > be fine with merging them.
>
> Great, thanks. No need for you to refresh me: if I do go ahead with
> merging them (not my current priority), it'll be obvious from whatever
> patch I show against -mm, what change you'd want to make to your tree.
Please go ahead and merge them. I suspect ARM not scanning i_mmap
is a bug.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-04-29 15:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 23:59 [PATCH] rmap 14 i_shared_lock fixes Hugh Dickins
2004-04-28 0:01 ` [PATCH] rmap 15 vma_adjust Hugh Dickins
2004-04-28 0:02 ` [PATCH] rmap 16 pretend prio_tree Hugh Dickins
2004-04-28 0:03 ` [PATCH] rmap 17 real prio_tree Hugh Dickins
2004-04-28 0:04 ` [PATCH] rmap 18 i_mmap_nonlinear Hugh Dickins
2004-04-28 23:11 ` Rik van Riel
2004-04-28 23:44 ` William Lee Irwin III
2004-04-29 6:10 ` Hugh Dickins
2004-04-29 6:32 ` William Lee Irwin III
2004-04-29 13:43 ` James Bottomley
2004-04-29 14:24 ` Hugh Dickins
2004-04-29 15:20 ` Russell King [this message]
2004-04-28 0:06 ` [PATCH] rmap 19 arch prio_tree Hugh Dickins
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=20040429162020.J16407@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=vrajesh@umich.edu \
--cc=wli@holomorphy.com \
/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