public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: me@felipebalbi.com
Cc: Tony Lindgren <tony@atomide.com>, linux-omap@vger.kernel.org
Subject: Re: Git tree updated to v2.6.28-rc2, old sound and v4l drivers removed
Date: Mon, 27 Oct 2008 19:08:27 -0700	[thread overview]
Message-ID: <200810271908.28099.david-b@pacbell.net> (raw)
In-Reply-To: <20081028012538.GA32518@frodo>

On Monday 27 October 2008, Felipe Balbi wrote:
> we should get anything out of drivers/i2c/chips since Jean wanna get rid
> of that directory. So if you apply the patches I wrote to lp5521 I'm
> fixing a few stuff and moving that driver to drivers/leds. After that I
> could send that driver to Richard.

I have a hard time seeing that directory vanish *too* quickly,
but it's true that the linux-omap drivers now living only there
should be moved ...

There's gpio_expander_omap.c there, which seems to be used
exclusively by H3 and H4 board support.  Luckily I have some
patches to remove that from H4 sitting around somewhere (and
not *completely* dust-encrusted) so that's partly done already.


We have a good start on moving the twl4030 stuff out, but
there's work yet to be done on that.  The USB transceiver
stuff is probably the most significant bit.  I could see
that, and some other bits, living in a drivers/usb/otg
directory.

- Dave

  reply	other threads:[~2008-10-28  2:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-27 20:43 Git tree updated to v2.6.28-rc2, old sound and v4l drivers removed Tony Lindgren
2008-10-28  1:25 ` Felipe Balbi
2008-10-28  2:08   ` David Brownell [this message]
2008-10-28  3:07   ` Tony Lindgren
2008-10-28 10:57     ` Felipe Balbi
2008-10-28 16:31       ` David Brownell
2008-10-29  7:08 ` David Brownell
2008-10-29 19:30 ` 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=200810271908.28099.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-omap@vger.kernel.org \
    --cc=me@felipebalbi.com \
    --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