From: Greg KH <gregkh@linuxfoundation.org>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: "Chen, Jamie" <jamie.chen@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Alan Stern <stern@rowland.harvard.edu>,
USB list <linux-usb@vger.kernel.org>,
"Tsai, Gaggery" <gaggery.tsai@intel.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: EHCI host broken -- interrupts disabled
Date: Mon, 20 Jan 2014 12:36:36 -0800 [thread overview]
Message-ID: <20140120203636.GA30640@kroah.com> (raw)
In-Reply-To: <20140120193918.GD5545@xanatos>
On Mon, Jan 20, 2014 at 11:39:18AM -0800, Sarah Sharp wrote:
> On Mon, Jan 20, 2014 at 12:15:47PM +0000, Chen, Jamie wrote:
> > Try to apply this patch to kernel 3.8.0.
> >
> > Make sure the ehci can work fine and lspci show that PCI_COMMAND_INTX_DISABLE is 0.
> >
> > The patch can resolved this issue.
>
> Great! Thanks for testing, Jamie.
>
> Bjorn, can you add me to the Cc list for this patch? I'd like to notify
> other Linux distros when it lands so they can pick it up.
Might as well mark it for stable@vger.kernel.org, so that it does
automatically get propagated to the distros...
thanks,
greg k-h
next prev parent reply other threads:[~2014-01-20 20:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140114181721.GC12126@xanatos>
[not found] ` <Pine.LNX.4.44L0.1401141336020.1310-100000@iolanthe.rowland.org>
2014-01-16 17:32 ` EHCI host broken -- interrupts disabled Bjorn Helgaas
2014-01-16 19:40 ` Alan Stern
2014-01-17 18:22 ` Bjorn Helgaas
2014-01-20 12:15 ` Chen, Jamie
2014-01-20 19:39 ` Sarah Sharp
2014-01-20 20:36 ` Greg KH [this message]
2014-01-30 0:04 ` Bjorn Helgaas
2014-02-11 23:24 ` Bjorn Helgaas
[not found] ` <F01C6967BCFFB14E8DF7F5D2FD1053EB1ECC22@PGSMSX103.gar.corp.intel.com>
2014-02-14 20:47 ` Bjorn Helgaas
2014-02-14 22:27 ` Sarah Sharp
2014-02-14 22:37 ` Bjorn Helgaas
2014-01-21 19:15 ` USB EHCI broken on Celeron N2920 (Bay Trail) Sarah Sharp
2014-01-22 1:41 ` Chris Cheng
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=20140120203636.GA30640@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bhelgaas@google.com \
--cc=gaggery.tsai@intel.com \
--cc=jamie.chen@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sarah.a.sharp@linux.intel.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.