All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Gadiyar, Anand" <gadiyar@ti.com>
Cc: Bryan Wu <cooloney@kernel.org>,
	"me@felipebalbi.com" <me@felipebalbi.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] MUSB: Fix bug - don't mess up count number and CSR0 register value
Date: Tue, 5 Aug 2008 12:02:12 +0300	[thread overview]
Message-ID: <20080805090211.GG7193@atomide.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB02569B8800@dbde02.ent.ti.com>

* Gadiyar, Anand <gadiyar@ti.com> [080805 11:59]:
> > Hi,
> >
> > * Bryan Wu <cooloney@kernel.org> [080805 06:27]:
> > > Signed-off-by: Bryan Wu <cooloney@kernel.org>
> > > ---
> > >  drivers/usb/musb/musb_gadget_ep0.c |   24 ++++++++++++------------
> > >  1 files changed, 12 insertions(+), 12 deletions(-)
> >
> > I think all musb patches should be now posted to linux-usb list as the
> > patches are queued for integration.
> >
> > So I'll be using plain code coming from mainline tree and
> > won't apply any patches to musb code except temporary fixes if compile
> > breaks.
> >
> > Cheers,
> >
> > Tony
> 
> Do you mind if I post the patches here as well? It could be useful to
> someone using USB on OMAP? At least they could get a review here.

Yes, it's a good idea to Cc linux-omap list so people can test them
and keep track of the changes easier :)

> I've got one set of patches coming up over the next couple of days, and
> all of it is based on the current linux-omap tree.

OK

Tony

      reply	other threads:[~2008-08-05  9:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05  3:31 [PATCH] MUSB: Fix bug - don't mess up count number and CSR0 register value Bryan Wu
2008-08-05  8:45 ` Tony Lindgren
2008-08-05  8:49   ` Gadiyar, Anand
2008-08-05  9:02     ` Tony Lindgren [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=20080805090211.GG7193@atomide.com \
    --to=tony@atomide.com \
    --cc=cooloney@kernel.org \
    --cc=gadiyar@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=me@felipebalbi.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.