>-----Original Message----- >From: [email protected] >[mailto:[email protected]] On Behalf Of Tony >Lindgren >Sent: Friday, November 13, 2009 12:03 PM >To: Gadiyar, Anand >Cc: [email protected] >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. Only extra patch that I have to add is the 8250 patch, that needs posting separately. > >Regards, > >Tony >-- >To unsubscribe from this list: send the line "unsubscribe linux-omap" in >the body of a message to [email protected] >More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
