linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jacky.Cao@sony.com
Cc: oneukum@suse.com, stern@rowland.harvard.edu,
	linux-usb@vger.kernel.org, linux-scsi@vger.kernel.org,
	usb-storage@lists.one-eyed-alien.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: uas: fix usb subsystem hang after power off hub port
Date: Mon, 4 Mar 2019 07:23:25 +0100	[thread overview]
Message-ID: <20190304062325.GA2686@kroah.com> (raw)
In-Reply-To: <16EA1F625E922C43B00B9D8225022050086961B5@APYOKXMS108.ap.sony.com>

On Mon, Mar 04, 2019 at 02:08:54AM +0000, Jacky.Cao@sony.com wrote:
> ________________________________
> 
> This email is confidential and intended only for the use of the individual or entity named above and may contain information that is privileged. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify us immediately by return email or telephone and destroy the original message. - This mail is sent via Sony Asia Pacific Mail Gateway..

This footer requires me to delete this email as it is not compatible
with doing Linux kernel development.

greg k-h

       reply	other threads:[~2019-03-04  6:23 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16EA1F625E922C43B00B9D8225022050086961B5@APYOKXMS108.ap.sony.com>
2019-03-04  6:23 ` Greg KH [this message]
2019-03-04  7:19   ` [PATCH] usb: uas: fix usb subsystem hang after power off hub port Jacky.Cao
2019-03-08  9:13 Kento.A.Kobayashi
2019-03-08 16:52 ` Oliver Neukum
2019-03-08 17:33   ` Alan Stern
2019-03-11  8:36   ` Kento.A.Kobayashi
2019-03-12 15:37     ` Oliver Neukum
2019-03-15  2:28       ` Kento.A.Kobayashi
2019-03-25 10:21         ` Kento.A.Kobayashi
2019-03-25 10:34           ` Oliver Neukum
2019-03-28  7:53             ` Kento.A.Kobayashi
2019-03-28 15:15               ` Oliver Neukum
2019-03-28 15:57                 ` Alan Stern
2019-03-28 16:49                   ` Oliver Neukum
2019-03-29 14:13                     ` Alan Stern
2019-04-02  0:28                 ` Kento.A.Kobayashi
2019-04-02 14:38                   ` Alan Stern
2019-04-04  3:57                     ` Kento.A.Kobayashi
2019-04-04 19:33                       ` Alan Stern
2019-04-09  0:28                         ` Kento.A.Kobayashi
2019-04-09  1:21                           ` Alan Stern
2019-04-09  2:10                         ` Martin K. Petersen
2019-04-09 14:44                           ` Alan Stern
2019-04-09 15:16                             ` Bart Van Assche
2019-04-09 16:45                               ` Alan Stern
2019-04-15  0:27                                 ` Kento.A.Kobayashi
2019-04-15 15:18                                   ` Alan Stern
2019-04-15 15:32                                     ` Alan Stern
2019-04-16  2:31                                       ` Kento.A.Kobayashi
2019-04-10  2:11                               ` Martin K. Petersen

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=20190304062325.GA2686@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Jacky.Cao@sony.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=stern@rowland.harvard.edu \
    --cc=usb-storage@lists.one-eyed-alien.net \
    /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;
as well as URLs for NNTP newsgroup(s).