From: Ingo Molnar <mingo@elte.hu>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: mingo@redhat.com,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-kernel@vger.kernel.org
Subject: Re: why is kmap_prot not always a define?
Date: Tue, 4 Dec 2007 13:54:08 +0100 [thread overview]
Message-ID: <20071204125408.GC31590@elte.hu> (raw)
In-Reply-To: <BE453CED-64E1-46FD-8C13-D752F5B63A9D@kernel.crashing.org>
* Kumar Gala <galak@kernel.crashing.org> wrote:
> Is there some reason why kmap_prot isn't just a #define on all archs?
none that i can remember - why do you ask? Do you have some cleanup
idea?
Ingo
prev parent reply other threads:[~2007-12-04 12:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 22:16 why is kmap_prot not always a define? Kumar Gala
2007-12-04 12:54 ` Ingo Molnar [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=20071204125408.GC31590@elte.hu \
--to=mingo@elte.hu \
--cc=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
/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