From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: <gregkh@linuxfoundation.org>
Cc: <linux-usb@vger.kernel.org>,
Mathias Nyman <mathias.nyman@linux.intel.com>
Subject: [PATCH 0/1] fix xhci feature merge issue in current usb-next
Date: Mon, 16 May 2022 12:48:49 +0300 [thread overview]
Message-ID: <20220516094850.19788-1-mathias.nyman@linux.intel.com> (raw)
Hi Greg
Two different conflicting features touching xhci got into current usb-next
for 5.19
One adds support for xHC hosts with just one roothub,
second adds support to defer first roothub registration until second
roothub is added.
commit 873f323618c2 ("xhci: prepare for operation w/o shared hcd")
commit b7a4f9b5d0e4 ("xhci: Set HCD flag to defer primary roothub
registration")
We ended up trying to defer roothub registratinog for xHC with just one
roothub.
This patch fixes the issue and goes on top of current usb-next
This patch shouldn't be needed for stable as the new feature to support
one roothub xHC isn't marked for stable either, but setting Fixes flag
in case someone later picks it up for stable.
Mathias Nyman (1):
xhci: Don't defer primary roothub registration if there is only one
roothub
drivers/usb/host/xhci.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
2.25.1
next reply other threads:[~2022-05-16 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 9:48 Mathias Nyman [this message]
2022-05-16 9:48 ` [PATCH 1/1] xhci: Don't defer primary roothub registration if there is only one roothub Mathias Nyman
2022-05-19 16:10 ` [PATCH 0/1] fix xhci feature merge issue in current usb-next Greg KH
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=20220516094850.19788-1-mathias.nyman@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.