All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-omap@vger.kernel.org
Subject: Re: [patch 2.6.28-rc6-omap-git 0/5] drivers/usb/otg seeding
Date: Mon, 15 Dec 2008 11:11:20 -0800	[thread overview]
Message-ID: <20081215191120.GD10664@atomide.com> (raw)
In-Reply-To: <200812011311.25404.david-b@pacbell.net>

* David Brownell <david-b@pacbell.net> [081201 13:55]:
> These five patches go on top of the two twl4030-usb patches sent
> last Wednesday.
> 
> The first four are in the USB queue (though the fourth has some
> minor updates that haven't yet made it there, like speling Tony's
> name right) ... the last one moves one more OMAP-only driver out
> of drivers/i2c/chips, to help it swim upstream.
> 
>  - move drivers/i2c/chips/isp1301-omap.c to drivers/usb/otg
>  - add new gpio_vbus "transceiver" (not used for now with OMAP)
>  - add missing otg_put_transceiver() call
>  - move OMAP's transceiver glue to drivers/usb/otg
>  - move drivers/i2c/chips/twl4030-usb.c to drivers/usb/otg
> 
> That last patch is the one which will break if the two preceding
> patches aren't applied.
> 
> After this the twl4030-usb code will more or less be ready to
> go upstream ... doesn't yet use regulator framework, but that's
> not upstream either.

Great. Pushing these to l-o tree today.

Tony


> 
> - Dave
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2008-12-15 19:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01 21:11 [patch 2.6.28-rc6-omap-git 0/5] drivers/usb/otg seeding David Brownell
2008-12-15 19:11 ` Tony Lindgren [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=20081215191120.GD10664@atomide.com \
    --to=tony@atomide.com \
    --cc=david-b@pacbell.net \
    --cc=linux-omap@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.