From: Maarten Lankhorst <m.b.lankhorst@gmail.com>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@kernel.org
Subject: Re: [stable] [PATCH 2/2] xhci: Do not issue device reset when device is not setup
Date: Thu, 02 Jun 2011 01:02:06 +0200 [thread overview]
Message-ID: <4DE6C4EE.8020807@gmail.com> (raw)
In-Reply-To: <20110601224205.GC13079@xanatos>
Hi Sarah,
Op 02-06-11 00:42, Sarah Sharp schreef:
> Maarten, if you feel a patch needs to be added to the stable trees,
> please just add this line below your Signed-off-by line:
>
> Cc: stable@kernel.org
>
> Don't Cc stable in your initial RFC patches. Once they're done, I'll
> queue them to my xHCI tree and send them off to Greg. When Greg sends
> them off to Linus for inclusion into 3.0, the patches will automatically
> get picked up into the stable tree.
Sorry about that. I interpreted cc'ing stable wrongly, feel like such a
noob on this whole submitting patches thing. :)
I do think it needs inclusion in stable though, since it fixes the
xhci controller that so far never worked for me, although the earliest
kernel I tested on was v2.6.33.$x-rt$y. Didn't test the patch though,
but iirc the failure mode wasn't any different.
~Maarten
next prev parent reply other threads:[~2011-06-01 23:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 21:27 [PATCH 1/2] xhci: Add defines for hardcoded slot states Maarten Lankhorst
2011-06-01 21:27 ` [PATCH 2/2] xhci: Do not issue device reset when device is not setup Maarten Lankhorst
2011-06-01 22:17 ` [stable] " Greg KH
2011-06-01 22:42 ` Sarah Sharp
2011-06-01 23:02 ` Maarten Lankhorst [this message]
2011-06-01 23:32 ` Sarah Sharp
2011-06-02 11:35 ` Maarten Lankhorst
2011-06-01 22:17 ` [stable] [PATCH 1/2] xhci: Add defines for hardcoded slot states 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=4DE6C4EE.8020807@gmail.com \
--to=m.b.lankhorst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sarah.a.sharp@linux.intel.com \
--cc=stable@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