From: Thomas Gleixner <tglx@linutronix.de>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org
Subject: Re: [PATCH 1/2] x86: unify kmap_atomic_pfn() and iomap_atomic_prot_pfn()
Date: Wed, 11 Mar 2009 16:08:33 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.0903111606350.29264@localhost.localdomain> (raw)
In-Reply-To: <20090311143317.GA22244@localhost.localdomain>
On Wed, 11 Mar 2009, Akinobu Mita wrote:
> kmap_atomic_pfn() and iomap_atomic_prot_pfn() are almost same except
> pgprot. This patch removes the code duplication for these two functions.
How exaclty does this compile with CONFIG_HIGHMEM=n ?
Thanks,
tglx
next prev parent reply other threads:[~2009-03-11 15:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 14:33 Akinobu Mita
2009-03-11 14:34 ` [PATCH 2/2] x86: debug check for kmap_atomic_pfn " Akinobu Mita
2009-03-11 16:54 ` [tip:x86/mm] " Akinobu Mita
2009-03-11 15:08 ` Thomas Gleixner [this message]
2009-03-11 15:25 ` [PATCH 1/2] x86: unify kmap_atomic_pfn() " Akinobu Mita
2009-03-11 16:52 ` Ingo Molnar
2009-03-12 0:28 ` Akinobu Mita
2009-03-12 12:24 ` Ingo Molnar
2009-03-12 12:27 ` Ingo Molnar
2009-03-11 16:54 ` [tip:x86/mm] " Akinobu Mita
2009-03-13 1:39 ` [tip:x86/mm] x86: unify kmap_atomic_pfn() and iomap_atomic_prot_pfn(), fix Ingo Molnar
2009-03-14 4:19 ` [PATCH -tip 1/2] mm: introduce debug_kmap_atomic Akinobu Mita
2009-03-14 4:20 ` [PATCH -tip 2/2] mm: use debug_kmap_atomic Akinobu Mita
2009-03-14 13:15 ` [PATCH -tip 1/2] mm: introduce debug_kmap_atomic Ingo Molnar
2009-03-15 15:15 ` Akinobu Mita
2009-03-15 20:45 ` [tip:x86/mm] x86, mm: remove unnecessary include file from iomap_32.c Akinobu Mita
2009-03-23 0:23 ` [PATCH -tip 1/2] mm: introduce debug_kmap_atomic Andrew Morton
2009-03-24 6:21 ` Akinobu Mita
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=alpine.LFD.2.00.0903111606350.29264@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=akinobu.mita@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®