From: Tony Lindgren <tony@atomide.com>
To: Kalle Valo <kalle.valo@iki.fi>
Cc: Felipe Balbi <felipe.balbi@nokia.com>,
Max Filippov <jcmvbkbc@gmail.com>,
Jarkko Nikula <jhnikula@gmail.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: N8x0 to mainline patches
Date: Fri, 7 Aug 2009 10:03:20 +0300 [thread overview]
Message-ID: <20090807070317.GR2358@atomide.com> (raw)
In-Reply-To: <da94abde0908060927s57a5bdcfxac4e46db16913820@mail.gmail.com>
* Kalle Valo <kalle.valo@iki.fi> [090806 19:29]:
> On Thu, Aug 6, 2009 at 7:21 PM, Kalle Valo<kalle.valo@iki.fi> wrote:
> > My plan is this:
> >
> > 1. first finish OMAP_TAG_UART removal patch and send it for review
This would be great.
> > 2. finins and send tusb6010 patch
> >
> > + omap2-add-usb-tusb6010-c
The tusb6010 could be added later on as a fix too if you want to cut
down dependencies.
> > 2. fold these n8x0 board file patches into one and send it for review:
> >
> > + n8x0-add-board-file
> > + n8x0-onenand-support
> > + n8x0-add-spi-support
> > + n8x0-add-usb-support
Yeh one patch for the board file.
> This was item 3, of course. And I forget n8x0_defconfig, I'll send
> that as a separate patch.
Yeah it's easier to read the series that way.
> Tony, does this look ok to you?
Looks good to me!
Tony
next prev parent reply other threads:[~2009-08-07 7:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 5:51 N8x0 to mainline patches Kalle Valo
2009-07-13 6:03 ` Felipe Balbi
2009-07-13 6:51 ` Kalle Valo
2009-07-13 6:53 ` Felipe Balbi
2009-08-06 7:10 ` Tony Lindgren
2009-08-06 16:21 ` Kalle Valo
2009-08-06 16:27 ` Kalle Valo
2009-08-07 7:03 ` Tony Lindgren [this message]
2009-08-07 7:44 ` Kalle Valo
2009-08-07 7:51 ` Tony Lindgren
2009-08-07 7:04 ` Tony Lindgren
2009-07-13 19:52 ` green
-- strict thread matches above, loose matches on Subject: below --
2009-07-13 14:49 Luke-Jr
2009-07-14 5:10 ` Kalle Valo
2009-07-15 16:19 ` Arnaud Ebalard
2009-07-19 21:00 Luke-Jr
2009-07-20 7:23 ` Arnaud Ebalard
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=20090807070317.GR2358@atomide.com \
--to=tony@atomide.com \
--cc=felipe.balbi@nokia.com \
--cc=jcmvbkbc@gmail.com \
--cc=jhnikula@gmail.com \
--cc=kalle.valo@iki.fi \
--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.