From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754564AbcANU1V (ORCPT ); Thu, 14 Jan 2016 15:27:21 -0500 Received: from tex.lwn.net ([70.33.254.29]:42582 "EHLO vena.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751074AbcANU1S (ORCPT ); Thu, 14 Jan 2016 15:27:18 -0500 Date: Thu, 14 Jan 2016 13:27:16 -0700 From: Jonathan Corbet To: Borislav Petkov Cc: Eric Morton , linux-doc@vger.kernel.org, LKML Subject: Re: [PATCH] Documentation: Explain pci=conf1,conf2 more verbosely Message-ID: <20160114132716.761edc01@lwn.net> In-Reply-To: <1452700131-17557-1-git-send-email-bp@alien8.de> References: <1452700131-17557-1-git-send-email-bp@alien8.de> Organization: LWN.net X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 13 Jan 2016 16:48:51 +0100 Borislav Petkov 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