public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <me@felipebalbi.com>
To: Greg KH <greg@kroah.com>
Cc: David Brownell <david-b@pacbell.net>,
	ajay.gupta@ti.com, linux-omap@vger.kernel.org,
	linux-usb@vger.kernel.org, felipe.balbi@nokia.com
Subject: Re: [PATCH] OMAP:MUSB: Fixes the TT programming.
Date: Mon, 25 Aug 2008 10:57:13 +0300	[thread overview]
Message-ID: <20080825075712.GA9910@frodo> (raw)
In-Reply-To: <20080825035322.GC3128@kroah.com>

On Sun, Aug 24, 2008 at 08:53:22PM -0700, Greg KH wrote:
> On Thu, Aug 21, 2008 at 11:30:06PM -0700, David Brownell wrote:
> > On Thursday 21 August 2008, ajay.gupta@ti.com wrote:
> > > From: Ajay Kumar Gupta <ajay.gupta@ti.com>
> > > 
> > > Fixes enumeration failures when a USB device attached to a LS hub
> > > is connected to OMAP EVM via HS hub. This is fixed by correctly
> > > programming hub address register in enqueue path.  
> > > 
> > > Signed-off-by: Ajay Kumar Gupta <ajay.gupta@ti.com>
> > 
> > Looks right to me, other than the lack of line wrapping in that
> > summary (corrected above).  Moreover, there ought to be some way
> > to make all high speed hosts share TT scheduling code ... ;)
> > 
> > Acked-by: David Brownell <dbrownell@users.sourceforge.net>
> 
> Ok, for all MUSB patches, I'm going to wait until Felipe tells me to
> accept them, as he's the subsystem/driver maintainer.
> 
> Felipe, is this ok?  Can you just bundle up what you feel is good and
> send them to me when they are ready (usually as soon as possible)?

Ok. I'll queue them today and send to you in a few hours.

-- 
balbi

      reply	other threads:[~2008-08-25  7:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-22  6:13 [PATCH] OMAP:MUSB: Fixes the TT programming ajay.gupta-l0cyMroinI0
2008-08-22  6:30 ` David Brownell
     [not found]   ` <200808212330.06650.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-08-25  3:53     ` Greg KH
2008-08-25  7:57       ` Felipe Balbi [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=20080825075712.GA9910@frodo \
    --to=me@felipebalbi.com \
    --cc=ajay.gupta@ti.com \
    --cc=david-b@pacbell.net \
    --cc=felipe.balbi@nokia.com \
    --cc=greg@kroah.com \
    --cc=linux-omap@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