From: Kyle McMartin <kyle@mcmartin.ca>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-mm <linux-mm@kvack.org>,
linux-arch <linux-arch@vger.kernel.org>,
Parisc List <linux-parisc@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] parisc: fix compile failure with kmap_atomic changes
Date: Thu, 28 Oct 2010 10:16:16 -0400 [thread overview]
Message-ID: <20101028141616.GY8332@bombadil.infradead.org> (raw)
In-Reply-To: <1288204547.6886.23.camel@mulgrave.site>
On Wed, Oct 27, 2010 at 01:35:47PM -0500, James Bottomley wrote:
> Author: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Date: Tue Oct 26 14:21:51 2010 -0700
>
> mm: stack based kmap_atomic()
>
> overlooked the fact that parisc uses kmap as a coherence mechanism, so
> even though we have no highmem, we do need to supply our own versions of
> kmap (and atomic). This patch converts the parisc kmap to the form
> which is needed to keep it compiling (it's a simple prototype and name
> change).
>
> Signed-off-by: James Bottomley <James.Bottomley@suse.de>
Signed-off-by: Kyle McMartin <kyle@redhat.com>
Care to send it straight to Linus? I didn't want to rebase my tree to
pull in the fix and risk his wrath...
Thanks,
--Kyle
--
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:[~2010-10-28 14:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 18:35 [PATCH] parisc: fix compile failure with kmap_atomic changes James Bottomley
2010-10-28 5:18 ` John David Anglin
2010-10-28 14:03 ` James Bottomley
2010-10-28 17:13 ` John David Anglin
2010-10-28 17:39 ` James Bottomley
2010-10-28 18:11 ` John David Anglin
2010-10-28 14:16 ` Kyle McMartin [this message]
2010-10-28 14:26 ` James Bottomley
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=20101028141616.GY8332@bombadil.infradead.org \
--to=kyle@mcmartin.ca \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-parisc@vger.kernel.org \
--cc=peterz@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).