From: "H. Peter Anvin" <hpa@zytor.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Jeff Garzik <jeff@garzik.org>,
ak@suse.de, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Document x86-64 iommu kernel parameters
Date: Tue, 02 Oct 2007 21:10:06 -0700 [thread overview]
Message-ID: <4703161E.8040603@zytor.com> (raw)
In-Reply-To: <20071002210125.85b84add.randy.dunlap@oracle.com>
Randy Dunlap wrote:
>
> Maybe we can/should merge the doc files along with the x86 arch merge.
>
Well, the x86 merge is pretty much mechanical. It should be followed up
with a lot of manual merging.
-hpa
next prev parent reply other threads:[~2007-10-03 4:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 1:34 [PATCH] Document x86-64 iommu kernel parameters Jeff Garzik
2007-10-03 2:22 ` Randy Dunlap
2007-10-03 2:30 ` Jeff Garzik
2007-10-03 3:42 ` Randy Dunlap
2007-10-03 4:01 ` Randy Dunlap
2007-10-03 4:10 ` H. Peter Anvin [this message]
2007-10-03 16:58 ` Chuck Ebbert
2007-10-04 9:01 ` Andi Kleen
2007-10-04 15:50 ` Chuck Ebbert
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=4703161E.8040603@zytor.com \
--to=hpa@zytor.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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