From: Jonathan Corbet <corbet@lwn.net>
To: Borislav Petkov <bp@alien8.de>
Cc: Eric Morton <Eric.Morton@amd.com>,
linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation: Explain pci=conf1,conf2 more verbosely
Date: Thu, 14 Jan 2016 13:27:16 -0700 [thread overview]
Message-ID: <20160114132716.761edc01@lwn.net> (raw)
In-Reply-To: <1452700131-17557-1-git-send-email-bp@alien8.de>
On Wed, 13 Jan 2016 16:48:51 +0100
Borislav Petkov <bp@alien8.de> wrote:
> People complained that setting the PCI config space access mechanism
> through "pci=conf1" or "pci=conf2" on the command line is not really
> documented. Yeah, can you blame them? Look at what we have now.
>
> So try to improve the situation a bit by explaining what those "conf1"
> and "conf2" things actually mean.
Seems good, applied to the docs tree...
> See http://wiki.osdev.org/PCI for more info.
...but I took the liberty of adding this URL too; people reading the
document are unlikely to check the commit log in case there's a useful
pointer waiting there for them :)
Thanks,
jon
next prev parent reply other threads:[~2016-01-14 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 15:48 [PATCH] Documentation: Explain pci=conf1,conf2 more verbosely Borislav Petkov
2016-01-14 20:27 ` Jonathan Corbet [this message]
2016-01-14 20:51 ` Borislav Petkov
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=20160114132716.761edc01@lwn.net \
--to=corbet@lwn.net \
--cc=Eric.Morton@amd.com \
--cc=bp@alien8.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.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