From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Hugh Dickins <hugh@veritas.com>
Cc: Matt Mackall <mpm@selenic.com>, Nick Piggin <npiggin@suse.de>,
David Howells <dhowells@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mm: unify shmem and tiny-shmem
Date: Thu, 2 Oct 2008 15:38:25 +1000 [thread overview]
Message-ID: <200810021538.25314.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0810011817060.19654@blonde.site>
On Thursday 02 October 2008 04:39, Hugh Dickins wrote:
> On Tue, 30 Sep 2008, Matt Mackall wrote:
> > (This applies on top of Nick's second tiny-shmem patch, which hasn't
> > made it to mainline yet(!).
>
> Gosh, thanks for mentioning that, you're right, it hasn't. I saw
> git pull updating mm/tiny-shmem.c a few days ago, and took it for
> granted that that was the #ifndef CONFIG_MMU fixed version; but it
> was the earlier one without that fix, despite us all knowing that
> fix was needed. I'd have pushed it myself for -rc8 if I'd realized
> it was still missing: Nick, please push it to Linus a.s.a.p. (with
> Acks from Matt and David and me) - or ask me to do so (I'm not sure
> when Andrew is back up and running).
Linus must have missed it I guess, because I think I did address it to
him.
If you or Matt or Andrew push it up, it might get taken seriously ;)
next prev parent reply other threads:[~2008-10-02 5:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 23:49 [PATCH] mm: unify shmem and tiny-shmem Matt Mackall
2008-10-01 15:00 ` David Howells
2008-10-01 18:39 ` Hugh Dickins
2008-10-02 5:38 ` Nick Piggin [this message]
2008-10-02 18:57 ` Matt Mackall
2008-10-02 22:23 ` David Howells
2008-10-02 22:44 ` Matt Mackall
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=200810021538.25314.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=npiggin@suse.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.