From mboxrd@z Thu Jan 1 00:00:00 1970 From: Albert ARIBAUD Date: Fri, 18 Feb 2011 00:00:49 +0100 Subject: [U-Boot] [PATCH] ARM: Update mach-types In-Reply-To: <20110217224755.E19D81539C5@gemini.denx.de> References: <1297890945-13674-1-git-send-email-s-paulraj@ti.com> <4D5D0CC8.30306@free.fr> <0554BEF07D437848AF01B9C9B5F0BC5DC192B820@dlee01.ent.ti.com> <4D5D5BA6.2000707@free.fr> <0554BEF07D437848AF01B9C9B5F0BC5DC192BF29@dlee01.ent.ti.com> <4D5DA3D7.6030908@free.fr> <20110217224755.E19D81539C5@gemini.denx.de> Message-ID: <4D5DA8A1.8010407@free.fr> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Le 17/02/2011 23:47, Wolfgang Denk a ?crit : > Dear Albert ARIBAUD, > > In message<4D5DA3D7.6030908@free.fr> you wrote: >> >> Because the merge window is closed and thus, only patches that were >> submitted initially before closure, or bug fixes, can go into master >> right now. > > I think we should make sure that the upcoming release uses a somewhat > recent version of the mach-types.h file. So please make here an > exception and apply these changes. As you wish. Only I'll have to re-send a pull request :) -- do I re-send a full one or just a delta wrt the previous one? > Actually I think it might be a good idea if we could always re-sync > mach-types.h agaist the current Linux kernel version before we publish > any release candidates and releases. What do you think? The only risk that I can see is renamings like the three ones I've noted; these will break the corresponding boards I think -- but admittedly the fix is trivial. > Best regards, > > Wolfgang Denk Amicalement, -- Albert.