From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Gongwei Li <lifangpi@hotmail.com>,
mathias.nyman@intel.com, gregkh@linuxfoundation.org
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
ligongwei@kylinos.cn
Subject: Re: [PATCH V1] usb: Fix typo in comment
Date: Mon, 19 Dec 2022 17:44:29 +0200 [thread overview]
Message-ID: <90f6c531-1fed-2d0a-c6a9-46685517f02b@linux.intel.com> (raw)
In-Reply-To: <SI2PR02MB4603295B418781879CE88751DDE59@SI2PR02MB4603.apcprd02.prod.outlook.com>
On 19.12.2022 3.38, Gongwei Li wrote:
> From: Gongwei Li <ligongwei@kylinos.cn>
>
> Spelling mistake in comment.
>
> Signed-off-by: Gongwei Li <ligongwei@kylinos.cn>
> ---
> drivers/usb/host/pci-quirks.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/host/pci-quirks.c b/drivers/usb/host/pci-quirks.c
> index ef08d68b9714..9710425e69aa 100644
> --- a/drivers/usb/host/pci-quirks.c
> +++ b/drivers/usb/host/pci-quirks.c
> @@ -1103,10 +1103,10 @@ void usb_enable_intel_xhci_ports(struct pci_dev *xhci_pdev)
> pci_read_config_dword(xhci_pdev, USB_INTEL_USB2PRM,
> &ports_available);
>
> - dev_dbg(&xhci_pdev->dev, "Configurable USB 2.0 ports to hand over to xCHI: 0x%x\n",
> + dev_dbg(&xhci_pdev->dev, "Configurable USB 2.0 ports to hand over to xHCI: 0x%x\n",
> ports_available);
>
> - /* Write XUSB2PR, the xHC USB 2.0 Port Routing Register, to
> + /* Write XUSB2PR, the xHCI USB 2.0 Port Routing Register, to
xHC isn't a typo in this case, just refers to the actual xHC Extensible Host Controller itself.
The port routing register isn't part of the xHCI specification.
Thanks
-Mathias
prev parent reply other threads:[~2022-12-19 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 1:38 Gongwei Li
2022-12-19 1:59 ` Bagas Sanjaya
2022-12-19 15:44 ` Mathias Nyman [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=90f6c531-1fed-2d0a-c6a9-46685517f02b@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=lifangpi@hotmail.com \
--cc=ligongwei@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
/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
all inboxes | Powered by JetHome®