From: Chris Wilson <chris@chris-wilson.co.uk>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-arch@vger.kernel.org, Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] mm,x86: fix kmap_atomic_push vs ioremap_32.c
Date: Wed, 27 Oct 2010 12:15:45 +0100 [thread overview]
Message-ID: <b9dded$gtgeib@orsmga002.jf.intel.com> (raw)
In-Reply-To: <1288175638.15336.1538.camel@twins>
On Wed, 27 Oct 2010 12:33:58 +0200, Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> Christoph just complained about the same on IRC, the below seems to cure
> things for i386-defconfig with CONFIG_HIGHMEM=n
Compiles and boots on the misbehaving box.
Thanks,
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
--
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>
prev parent reply other threads:[~2010-10-27 11:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-18 15:53 [PATCH 0/5] mm, highmem: kmap_atomic rework -v3 Peter Zijlstra
2010-09-18 15:53 ` [PATCH 1/5] mm: strictly nested kmap_atomic Peter Zijlstra
2010-09-18 15:53 ` [PATCH 2/5] mm: stack based kmap_atomic Peter Zijlstra
2010-09-19 17:01 ` Linus Torvalds
2010-09-20 9:31 ` Peter Zijlstra
2010-09-18 15:53 ` [PATCH 3/5] mm: Remove pte_*map_nested() Peter Zijlstra
2010-09-18 15:53 ` [PATCH 4/5] perf, x86: Fix up kmap_atomic type Peter Zijlstra
2010-09-18 15:53 ` [PATCH 5/5] mm: highmem documentation Peter Zijlstra
2010-10-27 10:27 ` [PATCH 0/5] mm, highmem: kmap_atomic rework -v3 Chris Wilson
2010-10-27 10:33 ` [PATCH] mm,x86: fix kmap_atomic_push vs ioremap_32.c Peter Zijlstra
2010-10-27 11:15 ` Chris Wilson [this message]
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='b9dded$gtgeib@orsmga002.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.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).