From: Tony Lindgren <tony@atomide.com>
To: "Pandita, Vikram" <vikram.pandita@ti.com>
Cc: "Gadiyar, Anand" <gadiyar@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Some patches need reposting, inbox cleared, patchwork cleared
Date: Fri, 13 Nov 2009 10:15:50 -0800 [thread overview]
Message-ID: <20091113181550.GD3684@atomide.com> (raw)
In-Reply-To: <FCCFB4CDC6E5564B9182F639FC35608702FA689287@dbde02.ent.ti.com>
* Pandita, Vikram <vikram.pandita@ti.com> [091113 10:05]:
>
>
> >-----Original Message-----
> >From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Tony
> >Lindgren
> >Sent: Friday, November 13, 2009 12:03 PM
> >To: Gadiyar, Anand
> >Cc: linux-omap@vger.kernel.org
> >Subject: Re: Some patches need reposting, inbox cleared, patchwork cleared
> >
> >> > Tony,
> >> >
> >> > What happened to the 3630 support stuff that had been merged to
> >> > your master branch as of yesterday?
> >> >
> >> > - Anand
> >>
> >> I meant, I see these patches in for-next, but they're not present
> >> in the l-o master branch. Is this deliberate?
> >
> >Hmm, it should be all merged into master branch also:
> >
> >$ git log --pretty=oneline --grep=3630 -n100 master arch/arm/mach-omap2
> >1739bbc268aeffc8d3d040cf6493ef4399a1a181 omap: 3630sdp: introduce 3630 sdp board support
> >13ac7e77f407e4c529eb1cb058031f896fd3e80c omap: zoom3: introduce zoom3 board support
> >79c6fce9daa80936eba830c49b6c559f5ca6295d omap: zoom: drop i2c-1 speed to 2400
> >3efbe15e7755108268b9ed72d3b6c6539f671ebe omap: zoom: rename zoom2 name to generic zoom
> >97bd76cf5e5c18ddcc8d38f997ae7aec4db3bb01 omap: zoom2: split board file for software reuse
> >2c8681ac36b4247c26c5789f63de9f522436c1c5 omap3630: Set omap3630 MMC1 I/O speed to 52Mhz
> >9283cf8a9d21889fb838634e7017e84acf69e79f omap3630: Configure HSMMC1 to 4-bit
> >1a309b7370e5aa6d703eded1afc53218a205a71f omap3630: Add HSMMC related checks
> >1e9e0b997c30b81b2165fa68cad4411e6136a8d2 omap3: 3630: update is_chip variable
> >6fb081fb525c05aed6fee28bf73fe4ee1fe2d5bd omap3: Introduce OMAP3630
> >
> >Can you check and let me know if something is missing?
>
> I just verified booting zoom3 on l-o master, and its working fine.
OK good. Can you also try booting this patch from Felipe on 3630:
http://patchwork.kernel.org/patch/59540/
> Only extra patch that I have to add is the 8250 patch, that needs posting separately.
OK
Regards,
Tony
next prev parent reply other threads:[~2009-11-13 18:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 0:38 Some patches need reposting, inbox cleared, patchwork cleared Tony Lindgren
2009-11-13 4:41 ` Gadiyar, Anand
2009-11-13 4:44 ` Gadiyar, Anand
2009-11-13 18:03 ` Tony Lindgren
2009-11-13 18:06 ` Pandita, Vikram
2009-11-13 18:15 ` Tony Lindgren [this message]
2009-11-13 18:20 ` Pandita, Vikram
2009-11-13 19:07 ` Pandita, Vikram
2009-11-14 1:08 ` Tony Lindgren
2009-11-16 11:37 ` Aggarwal, Anuj
2009-11-16 20:59 ` Tony Lindgren
2009-11-13 18:29 ` Gadiyar, Anand
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=20091113181550.GD3684@atomide.com \
--to=tony@atomide.com \
--cc=gadiyar@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=vikram.pandita@ti.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