All of lore.kernel.org
 help / color / mirror / Atom feed
From: "'Greg KH'" <gregkh@linuxfoundation.org>
To: Alexis Cortes <alexis.cortes@ti.com>
Cc: "'Sarah Sharp'" <sarah.a.sharp@linux.intel.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, "'Quach,
	Brian'" <brian.quach@ti.com>,
	"'Llamas, Jorge'" <jorge.llamas@ti.com>
Subject: Re: [PATCH] usb: host: xhci: Compliance Mode port recovery
Date: Mon, 30 Jul 2012 14:47:13 -0700	[thread overview]
Message-ID: <20120730214713.GA12510@kroah.com> (raw)
In-Reply-To: <5016ed18.0730b60a.1211.ffffe227SMTPIN_ADDED@mx.google.com>

On Mon, Jul 30, 2012 at 03:22:52PM -0500, Alexis Cortes wrote:
> Hi Greg,
> 
> I'm sorry for my late response on this. First of all thanks for your reply
> and your feedback :) 
> 
> We have been discussing with one of our major customers the possibility of
> identifying the platforms with the failing piece of hardware
> (SN65LVPE502CP), and as you suggested they have provided some DMI strings we
> can check in order to identify the platforms where those devices were
> installed. 
> 
> I have modified the patch so it will be executed only on those platforms
> reporting the specified DMI strings. I also applied some other suggestions
> you made on your previous email.
> 
> I would really appreciate if you could take a look at the patch and give me
> your feedback. Do you think that the patch is now suitable to be included in
> future kernel releases? 

That's really up to Sarah, as she is the maintainer of this driver.

How about resending it in a format that it can be applied in, and she
will take it from there?

But, at first glance, yes, it's much nicer now that you are matching on
DMI entries, thanks for taking the time to do that.

thanks,

greg k-h

      parent reply	other threads:[~2012-07-30 21:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <002801cd4e68$a4b4f3a0$ee1edae0$@cortes@ti.com>
2012-06-19 22:39 ` [PATCH] usb: host: xhci: Compliance Mode port recovery Sarah Sharp
     [not found]   ` <004101cd4f33$755e8eb0$601bac10$@cortes@ti.com>
2012-06-21  0:07     ` Sarah Sharp
2012-06-21  0:32       ` Greg KH
     [not found]         ` <003001cd4fd3$a7648950$f62d9bf0$@cortes@ti.com>
2012-06-22  0:08           ` Sarah Sharp
2012-06-22  1:48             ` 'Greg KH'
2012-06-22 16:44               ` Sarah Sharp
     [not found]         ` <4fe35a44.82143c0a.4e83.62a8SMTPIN_ADDED@mx.google.com>
2012-06-22  1:40           ` 'Greg KH'
     [not found]       ` <003701cd4fde$fd969290$f8c3b7b0$@cortes@ti.com>
2012-06-22 16:32         ` Sarah Sharp
2012-06-22 16:47           ` Greg KH
     [not found]             ` <4fe9f0c8.04c1b60a.11cc.3ca4SMTPIN_ADDED@mx.google.com>
2012-06-26 17:51               ` 'Greg KH'
     [not found]                 ` <4ffcad84.6710b60a.2b1a.0065SMTPIN_ADDED@mx.google.com>
2012-07-11 15:06                   ` 'Greg KH'
     [not found]                     ` <5016ed18.0730b60a.1211.ffffe227SMTPIN_ADDED@mx.google.com>
2012-07-30 21:47                       ` 'Greg KH' [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=20120730214713.GA12510@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexis.cortes@ti.com \
    --cc=brian.quach@ti.com \
    --cc=jorge.llamas@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sarah.a.sharp@linux.intel.com \
    /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.