public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Li, Zhen-Hua (USL-China)" <zhen-hual@hp.com>
To: Alan Stern <stern@rowland.harvard.edu>, gregkh@linuxfoundation.org
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] usb,uhci: add a new tag for virtual uhci devices
Date: Thu, 27 Jun 2013 09:17:44 +0800	[thread overview]
Message-ID: <51CB92B8.7060706@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1306261516280.1880-100000@iolanthe.rowland.org>

Hi Alan,

I don't have a machine that this makes action different.

No matter whether it makes different, there is one thing will never change:
We create a patch to FIX a problem, not to avoid a problem.
Only when we can not fix it, we try to avoid it.

Thanks
ZhenHua

On 06/27/2013 03:17 AM, Alan Stern wrote:
> On Wed, 26 Jun 2013, Li, Zhen-Hua wrote:
>
>> From: "Li, Zhen-Hua" <zhen-hual@hp.com>
>>
>> There's another patch trying to fix this warning:
>>   "Controller not stopped yet!".
>> It is : 997ff893603c6455da4c5e26ba1d0f81adfecdfc .
>>
>> I don't think it is appropriate to avoid auto-stop for all HP uhci
>> devices. So add one  tag for the virtual uhci devices, it is used
>> to replace "wait_for_hp" in the auto-stop case.
> Do you have any machines where this makes a difference?
>
> Alan Stern
>
> .
>


  reply	other threads:[~2013-06-27  1:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-26  6:29 [PATCH 1/1] usb,uhci: add a new tag for virtual uhci devices Li, Zhen-Hua
2013-06-26 19:17 ` Alan Stern
2013-06-27  1:17   ` Li, Zhen-Hua (USL-China) [this message]
2013-06-27 15:52     ` Alan Stern
2013-06-28  1:05       ` Li, Zhen-Hua (USL-China)
2013-06-28 14:22         ` Alan Stern
2013-07-01  1:11           ` ZhenHua
2013-07-01 14:29             ` Alan Stern
2013-07-24 22:50 ` 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=51CB92B8.7060706@hp.com \
    --to=zhen-hual@hp.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox