Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Krzysztof Wilczyński" <kw@linux.com>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH] PCI: Fix typos
Date: Tue, 4 Mar 2025 10:20:14 -0600	[thread overview]
Message-ID: <20250304162014.GA227956@bhelgaas> (raw)
In-Reply-To: <20250304085722.GC2615015@rocinante>

On Tue, Mar 04, 2025 at 05:57:22PM +0900, Krzysztof Wilczyński wrote:
> 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

  reply	other threads:[~2025-03-04 16:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03 21:11 [PATCH] PCI: Fix typos Bjorn Helgaas
2025-03-04  8:57 ` Krzysztof Wilczyński
2025-03-04 16:20   ` Bjorn Helgaas [this message]
2025-03-04 16:31     ` Krzysztof Wilczyński
2025-03-04 16:01 ` Ilpo Järvinen
2025-03-04 16:58   ` Bjorn Helgaas
  -- strict thread matches above, loose matches on Subject: below --
2025-07-22 21:37 Bjorn Helgaas
2025-07-23  7:07 ` Thomas Gleixner
2024-11-02 17:45 Bjorn Helgaas

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=20250304162014.GA227956@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=kw@linux.com \
    --cc=linux-pci@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