public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Tony Lindgren <tony@atomide.com>, "Gadiyar, Anand" <gadiyar@ti.com>
Cc: "Pandita, Vikram" <vikram.pandita@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	Greg KH <greg@kroah.com>
Subject: Re: [PATCH] OMAP: USB EHCI: Support final revision of USB board
Date: Thu, 18 Sep 2008 12:22:53 -0700	[thread overview]
Message-ID: <200809181222.54393.david-b@pacbell.net> (raw)
In-Reply-To: <20080823232238.GL4713@atomide.com>

On Saturday 23 August 2008, Tony Lindgren wrote:
> 
> > I'll get the ehci-omap code in better shape and submit separately to the
> > linux-usb list.

Given that we've not yet seen patches splitting out the board-specific
bits into arch/arm/mach-omap2, I can't imagine those fixes being ready
for the 2.6.28 merge window.  (Hint for TI folk:  why not write the
code that way in the first place, avoiding all the delays inherent in
writing code you *know* is unsuitable for merging to mainline?)

They'd have to get in through the "new driver" exception ... but that
doesn't seem workable either, since the mach-omap2 updates aren't ready
yet *either*, and there's not much time left for them to get into the
OMAP tree, tested, reviewed for the ARM merge window, and then pulled
into Russell's patch queue ...

In short:  unless that's ready in the next few days, that stuff may
not be able to hit mainline until 2.6.29 merges start (I'm guessing
that will mean January 2009).


> Well we should really sync all usb code with mainline now that musb is
> merged.

There are still a bunch of essential musb build fixes waiting to get
into mainline (from moving include/asm-arm in RC1).

I cc'd Greg; I'm hoping he plans to get those upstream soon, so
the 2.6.28-rc0 merge window can focus on the remaining functional
updates to make platforms work ... instead of build fixes, and then
needing another merge window for functional fixes.  It seems DaVinci
will be ready (platform updates are in Russell's queue).  OMAP3 looks
to be more involved.

- Dave


  parent reply	other threads:[~2008-09-18 19:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-30 14:03 [PATCH] OMAP: USB EHCI: Support final revision of USB board Pandita, Vikram
2008-08-05 10:46 ` Tony Lindgren
2008-08-21 12:49   ` Gadiyar, Anand
2008-08-23 23:22     ` Tony Lindgren
2008-08-25  4:40       ` Gadiyar, Anand
2008-09-18 19:22       ` David Brownell [this message]
2008-09-18 19:49         ` Gadiyar, Anand
2008-09-18 20:00           ` Måns Rullgård
2008-09-18 20:06             ` Gadiyar, Anand
2008-09-18 20:29           ` David Brownell

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=200809181222.54393.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=gadiyar@ti.com \
    --cc=greg@kroah.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    --cc=vikram.pandita@ti.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