Re: [PATCH] PCI: Fix typos

["Krzysztof Wilczyński" <kw@linux.com>]

Hello,

[...]
> > > Fix typos and whitespace errors.
> > 
> > Oh nice!  Thank you for doing this!
> > 
> > While we are at this...  I wonder if we could also see about some things
> > that I often see in the code, too.  For example:
> > 
> >   - "pci" or "pcie" instead of "PCI" and "PCIe"
> >   - "PCIE", PCI-E" or "PCI-Express" over "PCIe" and "PCI Express", etc.
> >   - "aer" over "AER"
> >   - "translateable" over "translatable"
> >   - "SPCIFIC" over "SPECIFIC"
> >   - "OVERIDE" over "OVERRIDE"
> >   - "Root port" or "Root complex" over "Root Port", etc.
> >   - "dbi" over "DBI"
> >   - "requestor" vs "requester"
> >   - "fom" over "from"
> >   - "reserv" over "reserved"
> > 
> > Would be nice to get these also fixed up nicely since we are already
> > cleaning things up.
> 
> Locally fixed these:
> 
>   translateable -> translatable
>   SPCIFIC -> SPECIFIC
>   OVERIDE -> OVERRIDE
>   fom -> from

Thank you!

There are also some potentially awkward and/or not correctly formatted
comments in few places, per:

  drivers/pci/xen-pcifront.c
  641:	/*in case of we lost an aer request in four lines time_window*/
  642-	smp_mb__before_atomic();
  --
  702:	/*Flag for registering PV AER handler*/
  703-	set_bit(_XEN_PCIB_AERHANDLER, (void *)&pdev->sh_info->flags);
  
  drivers/pci/quirks.c
  3388:#endif /*CONFIG_MMC_RICOH_MMC*/
  3389-
  
  drivers/pci/hotplug/cpqphp_ctrl.c
  279:					/*FIXME
  280-					panic(msg_power_fault); */
  
  drivers/pci/hotplug/ibmphp_pci.c
  467:				/*_______________This is for debugging purposes only______________________________*/
  468-				debug("b4 writing, start address is %x\n", func->pfmem[count]->start);
  --
  471:				/*_________________________________________________________________________________*/
  472-
  --
  1053:	int howmany = 0;	/*this is to see if there are any devices behind the bridge */
  1054-
  
  drivers/pci/hotplug/cpqphp_core.c
  622:		/*FIXME: these capabilities aren't used but if they are
  623-		 *	 they need to be correctly implemented

This is something that always stands out to me when I am looking at this
code.  Not sure if we want to adjust these at some point or not.  Perhaps
now would also be a good time.

Thank you again!

	Krzysztof