On Fri, Mar 30, 2012 at 09:13:24PM +0800, Shawn Guo wrote: > On Thu, Jan 05, 2012 at 11:31:06AM +0000, Russell King - ARM Linux wrote: > > On Wed, Jan 04, 2012 at 09:18:00PM +0000, Russell King - ARM Linux wrote: > > > On Wed, Jan 04, 2012 at 09:52:05PM +0800, Shawn Guo wrote: > > > > On Mon, Dec 19, 2011 at 09:13:22AM +0000, Russell King - ARM Linux wrote: > > > > > No. It will be automatically removed from any update as long as it does > > > > > not conform to the requirements - that is, in this case, the strings > > > > > being out of sync indentified in the message to which you replied to. > > > > > > > > > > Someone needs to tell me what the correct entry is supposed to look like. > > > > > > > > > Hi Russell, > > > > > > > > Any chance to have APX4DEVKIT included in your patch 'ARM: Update > > > > mach-types' for 3.3? > > > > > > As it appears when I run the update script, the answer is yes. I'll > > > update the commit in the next couple of days (I want to reduce the > > > number of times I re-merge the tree now that I've a git-rerere immune > > > conflict to deal with.) > > > > I'll change that - as 3.2 was released last night. I'm not going to > > update mach-types now as that would be suicide - updating it will > > mean a bunch of entries will be deleted, and we don't know whether that > > will cause build failures. > > > > So... not this side of the merge window. > > Hi Russell, > > I thought you will send a mach-types update during v3.4 merge window, > so I merged APX4DEVKIT board file and it's now on mainline (not enabled > in mxs_defconfig though). But I have not seen mach-types update yet > while the merge window is almost done. Do you still plan to send an > update or plan to stop updating mach-types? Well, it seems I've been missing having that branch in linux-next for almost the entire previous cycle. It would be utterly irresponsible to now commit that into mainline because of the -now- huge number of platform IDs that it deletes. I assume, therefore, that you don't keep an eye on what's in linux-next. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/linux-arm-kernel