All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linyu Yuan <quic_linyyuan@quicinc.com>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
	Alan Stern <stern@rowland.harvard.edu>,
	linux-usb@vger.kernel.org, Jack Pham <quic_jackp@quicinc.com>,
	Wesley Cheng <quic_wcheng@quicinc.com>,
	Pratham Pratap <quic_ppratap@quicinc.com>
Subject: Re: [RFC PATCH 2/2] usb: core: hub: avoid reset hub during probe
Date: Fri, 3 Mar 2023 11:29:43 +0100	[thread overview]
Message-ID: <ZAHMFw9Bo6nWKGFO@kroah.com> (raw)
In-Reply-To: <1677835718-7405-2-git-send-email-quic_linyyuan@quicinc.com>

On Fri, Mar 03, 2023 at 05:28:38PM +0800, Linyu Yuan wrote:
> When start probe hub, during INIT, INTT2, INIT3 stage, when link state
> change to inactive, currently it will reset the device, maybe it will
> trigger warning in usb_submit_urb() due to urb->hcpriv is still active.

I am sorry, but I do not understand this text at all.  Can you reword
it?

> Add a flag name init_stage to avoid reset the device.

I do not understand, what is "flag name"?

thanks,

greg k-h

  reply	other threads:[~2023-03-03 10:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03  9:28 [RFC PATCH 1/2] usb: urb: show pipe information of warning message in usb_submit_urb() Linyu Yuan
2023-03-03  9:28 ` [RFC PATCH 2/2] usb: core: hub: avoid reset hub during probe Linyu Yuan
2023-03-03 10:29   ` Greg Kroah-Hartman [this message]
2023-03-03 16:05   ` Alan Stern
2023-03-08  5:54     ` Linyu Yuan
2023-03-08 16:04       ` Alan Stern
2023-03-09  2:18         ` Linyu Yuan
2023-03-09  2:49           ` Alan Stern
2023-03-03 10:28 ` [RFC PATCH 1/2] usb: urb: show pipe information of warning message in usb_submit_urb() Greg Kroah-Hartman

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=ZAHMFw9Bo6nWKGFO@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=quic_jackp@quicinc.com \
    --cc=quic_linyyuan@quicinc.com \
    --cc=quic_ppratap@quicinc.com \
    --cc=quic_wcheng@quicinc.com \
    --cc=stern@rowland.harvard.edu \
    /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.