From: David Cohen <david.a.cohen@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: alexander.shishkin@linux.intel.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] usb: chipidea: add Intel Clovertrail pci id
Date: Thu, 03 Oct 2013 09:04:04 -0700 [thread overview]
Message-ID: <524D9574.20702@linux.intel.com> (raw)
In-Reply-To: <20131003052134.GA1312@kroah.com>
Hi Greg,
On 10/02/2013 10:21 PM, Greg KH wrote:
> On Tue, Oct 01, 2013 at 02:32:58PM -0700, David Cohen wrote:
>> Signed-off-by: David Cohen <david.a.cohen@linux.intel.com>
>> ---
>> drivers/usb/chipidea/ci_hdrc_pci.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/drivers/usb/chipidea/ci_hdrc_pci.c b/drivers/usb/chipidea/ci_hdrc_pci.c
>> index 08a724b..d514332 100644
>> --- a/drivers/usb/chipidea/ci_hdrc_pci.c
>> +++ b/drivers/usb/chipidea/ci_hdrc_pci.c
>> @@ -129,6 +129,11 @@ static DEFINE_PCI_DEVICE_TABLE(ci_hdrc_pci_id_table) = {
>> PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0x0829),
>> .driver_data = (kernel_ulong_t)&penwell_pci_platdata,
>> },
>> + {
>> + /* Intel Clovertrail */
>> + PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0xe006),
>> + .driver_data = (kernel_ulong_t)&penwell_pci_platdata,
>> + },
>
> Can this go into 3.12-final, and any other stable kernel releases as
> well? Or does this platform also need other fixes that aren't in 3.10
> and 3.11?
This was tested on 3.10+
It might work on 3.4 but it's not validated. I can test it if we care
about chipidea on 3.4.
Br, David
>
> thanks,
>
> greg k-h
>
next prev parent reply other threads:[~2013-10-03 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 21:32 [PATCH v2 1/2] usb: chipidea: cosmetic clean up on pci id list David Cohen
2013-10-01 21:32 ` [PATCH v2 2/2] usb: chipidea: add Intel Clovertrail pci id David Cohen
2013-10-03 5:21 ` Greg KH
2013-10-03 16:04 ` David Cohen [this message]
2013-10-03 22:41 ` 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=524D9574.20702@linux.intel.com \
--to=david.a.cohen@linux.intel.com \
--cc=alexander.shishkin@linux.intel.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;
as well as URLs for NNTP newsgroup(s).