On Mon, Jul 30, 2018 at 10:18:37AM -0600, Logan Gunthorpe wrote: > Separate out the code to match a PCI device with a string (typically > originating from a kernel parameter) from the > pci_specified_resource_alignment() function into its own helper > function. > > While we are at it, this change fixes the kernel style of the function > (fixing a number of long lines and extra parentheses). > > Additionally, make the analogous change to the kernel parameter > documentation: Separating the description of how to specify a PCI device > into it's own section at the head of the pci= parameter. > > This patch should have no functional alterations. > > Signed-off-by: Logan Gunthorpe <logang@xxxxxxxxxxxx> > Reviewed-by: Stephen Bates <sbates@xxxxxxxxxxxx> > Acked-by: Christian König <christian.koenig@xxxxxxx> > Reviewed-by: Alex Williamson <alex.williamson@xxxxxxxxxx> > --- > Documentation/admin-guide/kernel-parameters.txt | 28 ++++- > drivers/pci/pci.c | 157 ++++++++++++++++-------- > 2 files changed, 126 insertions(+), 59 deletions(-) > > diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt > index 533ff5c68970..5cc215870ee1 100644 > --- a/Documentation/admin-guide/kernel-parameters.txt > +++ b/Documentation/admin-guide/kernel-parameters.txt > @@ -2994,7 +2994,26 @@ > See header of drivers/block/paride/pcd.c. > See also Documentation/blockdev/paride.txt. > > - pci=option[,option...] [PCI] various PCI subsystem options: > + pci=option[,option...] [PCI] various PCI subsystem options. > + > + Some options herein operate on a specific device > + or a set of devices (<pci_dev>). These are > + specified in one of the following formats: > + > + [<domain>:]<bus>:<slot>.<func> > + pci:<vendor>:<device>[:<subvendor>:<subdevice>] > + > + Note: the first format specifies a PCI > + bus/slot/function address which may change Unless you object, I'm going to change "slot" references like this to "device" so they match "BDF" and the language in the spec, which uses "slot" to refer to a physical slot and "device" when referring to geographical device addresses. I can do this when I apply these, so no need for you to repost them. Bjorn
