From: Tony Lindgren <tony@atomide.com>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: omap1710 upstream ?
Date: Thu, 18 May 2006 00:32:03 -0700 [thread overview]
Message-ID: <20060518073202.GB4013@atomide.com> (raw)
In-Reply-To: <1147890163.13483.6.camel@dwalker1.mvista.com>
* Daniel Walker <dwalker@mvista.com> [060517 11:22]:
>
> I was wondering if there was any time frame when omap1710 might be
> going upstream ? Is there still work that needs to be done to make it
> acceptable , or is it just not a top priority ?
In our tree omap1710 is mostly same as omap16xx. There are only few
places where we need to check for omap1710 vs omap16xx.
Most of the core omap code is in sync with mainline tree. Many device
drivers are not integrated yet.
Regards,
Tony
next prev parent reply other threads:[~2006-05-18 7:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 18:22 omap1710 upstream ? Daniel Walker
2006-05-18 7:32 ` Tony Lindgren [this message]
2006-05-18 13:34 ` Daniel Walker
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=20060518073202.GB4013@atomide.com \
--to=tony@atomide.com \
--cc=dwalker@mvista.com \
--cc=linux-omap-open-source@linux.omap.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