public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <me@felipebalbi.com>
Cc: Madhusudhan Chikkature <madhu.cr@ti.com>,
	linux-omap@vger.kernel.org, Mikko.K.Ylinen@nokia.com
Subject: Re: [Resending - PATCH 1/3] Triton BCI driver board/device setup for OMAP3430
Date: Tue, 5 Aug 2008 16:35:51 +0300	[thread overview]
Message-ID: <20080805133550.GJ7193@atomide.com> (raw)
In-Reply-To: <3db54da6fc6e74db523cc8e6bd2cf69d@felipebalbi.com>

* Felipe Balbi <me@felipebalbi.com> [080723 10:32]:
> 
> 
> On Wed, 23 Jul 2008 10:16:27 +0530, "Madhusudhan Chikkature"
> <madhu.cr@ti.com> wrote:
> > Hi Felipe,
> > 
> >> Tony, weird that we still have these prototypes in these headers.
> >> Could be some merging conflict ?
> > Yes. I see that these prototypes are still present in the board3430 and
> > board2430 header files in the omap tree.
> > 
> >> Anyways, please apply the attached patch. We're using
> >> usb_musb_init() and usb_ehci_init() now.
> > You mean I should apply the attached patch you sent for local use, right?
> > And I guess I dont need to resend this perticular BCI patch, am I
> correct?
> 
> No :-)
> 
> that was to Tony. Just replied to your mail so it's easy to see why we need
> that patch :-)

Pushing these today. Do you have a patch for moving the extern
prototypes into the twl header?

Tony

  reply	other threads:[~2008-08-05 13:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-22 11:55 [Resending - PATCH 1/3] Triton BCI driver board/device setup for OMAP3430 Madhusudhan Chikkature
2008-07-22 12:33 ` Felipe Balbi
2008-07-23  4:46   ` Madhusudhan Chikkature
2008-07-23  7:32     ` Felipe Balbi
2008-08-05 13:35       ` Tony Lindgren [this message]
2008-08-05 14:05         ` Felipe Balbi
2008-08-05 14:08           ` Tony Lindgren

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=20080805133550.GJ7193@atomide.com \
    --to=tony@atomide.com \
    --cc=Mikko.K.Ylinen@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=madhu.cr@ti.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox