From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Reilly Grant <grantr@vmware.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] xhci: Compute last_ctx from complete set of configured endpoints.
Date: Sun, 30 Jun 2013 14:08:16 -0700 [thread overview]
Message-ID: <20130630210816.GC4946@xanatos> (raw)
In-Reply-To: <215567179.20374384.1372091068135.JavaMail.root@vmware.com>
On Mon, Jun 24, 2013 at 09:24:28AM -0700, Reilly Grant wrote:
> On Mon, Jun 24, 2013 at 08:59AM -0700, Sarah Sharp wrote:
> > On Tue, Jun 18, 2013 at 02:09:13PM -0700, Reilly Grant wrote:
> >
> > So, no, I can't accept this patch. If this fixes a real problem in
> > some hardware, we'll add a quirk for that hardware.
>
> Thank you for the clarification. I was not aware of this addendum.
> Could you forward me a link to it? The last revision I can find on the
> Intel web site is from 05/2010.
The xHCI architect hasn't done an official release on the Intel site for
a while now. I think he's working on a bigger 1.1 release that includes
all the errata over the past couple years.
I think you can get the latest revision by emailing
xhcisupport@intel.com. If you don't hear back within a week or so,
email me back and I'll send you a PDF.
> This fixed a problem on VMware's virtual hardware. Assuming changing
> behavior will not affect any other systems I will fix it based on this
> information.
Yes, please fix this in VMware's virtual hardware.
Thanks,
Sarah Sharp
prev parent reply other threads:[~2013-06-30 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 21:09 [PATCH] xhci: Compute last_ctx from complete set of configured endpoints Reilly Grant
2013-06-24 15:59 ` Sarah Sharp
2013-06-24 16:24 ` Reilly Grant
2013-06-30 21:08 ` Sarah Sharp [this message]
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=20130630210816.GC4946@xanatos \
--to=sarah.a.sharp@linux.intel.com \
--cc=grantr@vmware.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox