All of lore.kernel.org
 help / color / mirror / Atom feed
From: harry@hebutterworth.freeserve.co.uk
To: xen-devel@lists.sourceforge.net
Subject: [PATCH] docs change: pci_dom0_hide -> physdev_dom0_hide
Date: Tue, 18 Jan 2005 10:54:50 +0100 (CET)	[thread overview]
Message-ID: <7211836.1106042090612.JavaMail.www@wwinf3001> (raw)

The documentation describing the parameter passed to Xen to hide PCI devices from the dom0 kernel is currently inconsistent with the code. This patch changes the documentation to match the implementation: the parameter name becomes physdev_dom0_hide and the example argument list is changed to contain a colon separator.

diff -Naur xen-unstable/docs/src/user.tex xen-unstable.new/docs/src/user.tex
--- xen-unstable/docs/src/user.tex      2005-01-18 04:37:38.000000000 +0000
+++ xen-unstable.new/docs/src/user.tex  2005-01-18 09:32:10.000000000 +0000
@@ -1770,7 +1770,7 @@
  possibilities are `bvt' (default), `atropos' and `rrobin'.
  For more information see Section~\ref{s:sched}.

-\item [pci\_dom0\_hide=(xx.xx.x)(yy.yy.y)\ldots ]
+\item [physdev\_dom0\_hide=(xx:xx.x)(yy:yy.y)\ldots ]
 Hide selected PCI devices from domain 0 (for instance, to stop it
 taking ownership of them so that they can be driven by another
 domain).  Device IDs should be given in hex format.  Bridge devices do


-- 

Whatever you Wanadoo:
http://www.wanadoo.co.uk/time/

This email has been checked for most known viruses - find out more at: http://www.wanadoo.co.uk/help/id/7098.htm


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

                 reply	other threads:[~2005-01-18  9:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=7211836.1106042090612.JavaMail.www@wwinf3001 \
    --to=harry@hebutterworth.freeserve.co.uk \
    --cc=xen-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.