public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <me@felipebalbi.com>
To: Felipe Balbi <felipe.balbi@nokia.com>
Cc: ext Tony Lindgren <tony@atomide.com>, linux-omap@vger.kernel.org
Subject: Re: Out of town next week
Date: Mon, 25 Aug 2008 19:13:40 +0300	[thread overview]
Message-ID: <20080825161339.GA7192@frodo> (raw)
In-Reply-To: <20080825114427.GF20450@gandalf.research.nokia.com>

On Mon, Aug 25, 2008 at 02:44:27PM +0300, Felipe Balbi wrote:
> On Mon, Aug 25, 2008 at 02:30:32PM +0300, Felipe Balbi wrote:
> > Cool, so we could get this week to merge drivers upstream. Attached is
> > (huge) series of missing omap drivers upstream. Anyone interested (that
> > have been working on the following drivers) should take them and
> > maintain them. After it gets merged, we should avoid applying patches
> > for those drivers to linux-omap and go through the proper mailing list.
> > This will take part of that job from tony and let driver writers take
> > care of them.
> > 
> > The only problem is that drivers will take a bit longer to get
> > up-to-date since Tony will get patches when merging back linus's tree to
> > l-o. On the other hand, the diff against mainline will decrease a lot
> > and Tony can focus on basic omap support.
> 
> Tony, if you're still there, I'd like to hear from you. Any comments ?
> 
> > Some drivers are needs some help:
> 
> typo, "some drivers that need some help"

I think the tarball didn't make it.

It's in http://felipebalbi.com/omap-drivers.tar.gz

-- 
balbi

      reply	other threads:[~2008-08-25 16:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-23 23:40 Out of town next week Tony Lindgren
     [not found] ` <20080825113032.GD20450@gandalf.research.nokia.com>
2008-08-25 11:44   ` Felipe Balbi
2008-08-25 16:13     ` 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=20080825161339.GA7192@frodo \
    --to=me@felipebalbi.com \
    --cc=felipe.balbi@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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