From: Borislav Petkov <bp@alien8.de>
To: Jonathan Corbet <corbet@lwn.net>
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 21:51:15 +0100 [thread overview]
Message-ID: <20160114205115.GI19941@pd.tnic> (raw)
In-Reply-To: <20160114132716.761edc01@lwn.net>
On Thu, Jan 14, 2016 at 01:27:16PM -0700, Jonathan Corbet wrote:
> > 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 :)
Fair enough.
We did have a little discussion about adding some URL which might
disappear in the future, to our docs. If it does, I guess we can then
fall back to the internet archive...
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
prev parent reply other threads:[~2016-01-14 20:51 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
2016-01-14 20:51 ` Borislav Petkov [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=20160114205115.GI19941@pd.tnic \
--to=bp@alien8.de \
--cc=Eric.Morton@amd.com \
--cc=corbet@lwn.net \
--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