From: "Neronin, Niklas" <niklas.neronin@linux.intel.com>
To: "Peter Chen (CIX)" <peter.chen@kernel.org>
Cc: mathias.nyman@linux.intel.com, linux-usb@vger.kernel.org
Subject: Re: [PATCH 0/7] usb: xhci: Port Register Set improvements
Date: Wed, 10 Sep 2025 10:12:30 +0300 [thread overview]
Message-ID: <971bf77d-da06-40d4-872d-b47a4a95f467@linux.intel.com> (raw)
In-Reply-To: <20250905015739.GA2473920@nchen-desktop>
On 05/09/2025 4.57, Peter Chen (CIX) wrote:
> On 25-09-04 17:42:13, Niklas Neronin wrote:
>> The aim of this patch set is to introduce tracing for PORTCS writes and
>
> I find several patches you are using PORTCS instead of PORTSC, is it typo?
>
Yes, it should be "PORTSC" (Port Status and Control). Good catch thanks!
Best Regards,
Niklas
prev parent reply other threads:[~2025-09-10 7:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 15:42 [PATCH 0/7] usb: xhci: Port Register Set improvements Niklas Neronin
2025-09-04 15:42 ` [PATCH 1/7] usb: xhci: correct indentation for PORTCS tracing function Niklas Neronin
2025-09-04 15:42 ` [PATCH 2/7] usb: xhci: align PORTCS trace with one-based port numbering Niklas Neronin
2025-09-04 15:42 ` [PATCH 3/7] usb: xhci: improve xhci_decode_portsc() Niklas Neronin
2025-09-04 15:42 ` [PATCH 4/7] usb: xhci: add tracing for PORTCS register writes Niklas Neronin
2025-09-04 15:42 ` [PATCH 5/7] usb: xhci: add USB Port Register Set struct Niklas Neronin
2025-09-04 15:42 ` [PATCH 6/7] usb: xhci: implement " Niklas Neronin
2025-09-04 15:42 ` [PATCH 7/7] usb: xhci: rename Port Register Set pointer in struct 'xhci_port' Niklas Neronin
2025-09-05 2:40 ` Peter Chen (CIX)
2025-09-10 7:24 ` Neronin, Niklas
2025-09-12 0:48 ` Peter Chen (CIX)
2025-09-05 1:57 ` [PATCH 0/7] usb: xhci: Port Register Set improvements Peter Chen (CIX)
2025-09-10 7:12 ` Neronin, Niklas [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=971bf77d-da06-40d4-872d-b47a4a95f467@linux.intel.com \
--to=niklas.neronin@linux.intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=peter.chen@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