From: Paul Mundt <lethal@linux-sh.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-arch@vger.kernel.org,
Linux Kernel List <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: [RESEND:PATCH] [ARM] clearpage: provide our own clear_user_highpage()
Date: Thu, 27 Nov 2008 10:07:55 +0900 [thread overview]
Message-ID: <20081127010755.GA30854@linux-sh.org> (raw)
In-Reply-To: <20081127102920.660303a5.sfr@canb.auug.org.au>
On Thu, Nov 27, 2008 at 10:29:20AM +1100, Stephen Rothwell wrote:
> Hi Russell,
>
> On Wed, 26 Nov 2008 11:19:59 -0600 James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> >
> > We'd like to pull this trick on parisc as well (another VIPT
> > architecture), so you can add my ack.
>
> If this is going to be used by more than one architecture during the next
> merge window, then maybe the change to include/linux/highmem.h could be
> extracted to its own patch and sent to Linus for inclusion in 2.6.28.
> This way we avoid some conflicts and the architectures can do their
> updates independently.
I plan to use it on VIPT SH also, so getting the higmem.h change in by
itself sooner rather than later would certainly be welcome.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-arch@vger.kernel.org,
Linux Kernel List <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: [RESEND:PATCH] [ARM] clearpage: provide our own clear_user_highpage()
Date: Thu, 27 Nov 2008 10:07:55 +0900 [thread overview]
Message-ID: <20081127010755.GA30854@linux-sh.org> (raw)
In-Reply-To: <20081127102920.660303a5.sfr@canb.auug.org.au>
On Thu, Nov 27, 2008 at 10:29:20AM +1100, Stephen Rothwell wrote:
> Hi Russell,
>
> On Wed, 26 Nov 2008 11:19:59 -0600 James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> >
> > We'd like to pull this trick on parisc as well (another VIPT
> > architecture), so you can add my ack.
>
> If this is going to be used by more than one architecture during the next
> merge window, then maybe the change to include/linux/highmem.h could be
> extracted to its own patch and sent to Linus for inclusion in 2.6.28.
> This way we avoid some conflicts and the architectures can do their
> updates independently.
I plan to use it on VIPT SH also, so getting the higmem.h change in by
itself sooner rather than later would certainly be welcome.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-11-27 1:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 17:13 [RESEND:PATCH] [ARM] clearpage: provide our own clear_user_highpage() Russell King
2008-11-26 17:13 ` Russell King
2008-11-26 17:19 ` James Bottomley
2008-11-26 17:19 ` James Bottomley
2008-11-26 23:29 ` Stephen Rothwell
2008-11-27 1:07 ` Paul Mundt [this message]
2008-11-27 1:07 ` Paul Mundt
2008-11-27 11:21 ` Russell King
2008-11-27 11:21 ` Russell King
2008-11-27 11:21 ` Russell King
2008-11-27 11:21 ` Russell King
2008-11-27 12:02 ` Hugh Dickins
2008-11-27 12:02 ` Hugh Dickins
2008-11-27 20:09 ` Paul Mundt
2008-11-27 20:09 ` Paul Mundt
2008-11-27 20:09 ` Paul Mundt
2008-11-27 20:09 ` Paul Mundt
2008-11-26 18:17 ` Hugh Dickins
2008-11-26 18:17 ` 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=20081127010755.GA30854@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=sfr@canb.auug.org.au \
/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.