From: Roland Dreier <rdreier@cisco.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
raisch@de.ibm.com, paulus@samba.org,
general@lists.openfabrics.org,
Hoang-Nam Nguyen <hnguyen@linux.vnet.ibm.com>
Subject: Re: [PATCH] ehca: map 4k firmware context of cq, qp to user space
Date: Thu, 02 Aug 2007 14:03:59 -0700 [thread overview]
Message-ID: <adawswd3ayo.fsf@cisco.com> (raw)
In-Reply-To: <200708021608.16436.arnd@arndb.de> (Arnd Bergmann's message of "Thu, 2 Aug 2007 16:08:15 +0200")
> remap_4k_pfn is defined in terms of remap_pfn_range if the base page
> size if 4k, so you don't need this #ifdef afaics.
Good point. I'll wait for an updated patch.
next prev parent reply other threads:[~2007-08-02 21:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 9:39 [PATCH] ehca: map 4k firmware context of cq, qp to user space Hoang-Nam Nguyen
2007-08-02 14:08 ` Arnd Bergmann
2007-08-02 21:03 ` Roland Dreier [this message]
2007-08-03 8:36 ` Hoang-Nam Nguyen
2007-08-08 14:13 ` Hoang-Nam Nguyen
2007-08-08 16:08 ` Roland Dreier
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=adawswd3ayo.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=arnd@arndb.de \
--cc=general@lists.openfabrics.org \
--cc=hnguyen@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=raisch@de.ibm.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;
as well as URLs for NNTP newsgroup(s).