From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnout Vandecappelle Date: Mon, 24 Feb 2014 20:16:24 +0100 Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-02-23 In-Reply-To: References: <20140224073008.3ECD8100F60@stock.ovh.net> <877g8kn6qf.fsf@dell.be.48ers.dk> Message-ID: <530B9A88.9010402@mind.be> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On 24/02/14 12:37, Thomas De Schampheleire wrote: > On Mon, Feb 24, 2014 at 11:30 AM, Peter Korsgaard wrote: >>>>>>> "Thomas" == Thomas De Schampheleire writes: >> >> >> >> tvheadend-c7d0335eb10d02b78... | 1 >> >> > Too old kernel headers (SYS_TURBO), patch available: >> > http://patchwork.ozlabs.org/patch/323403/ >> >> Yes, but that relies on the TOOLCHAIN_HEADERS_AT_LEAST_x stuff. Do we >> want that for 2014.02? > > It may be very short before the deadline for a patch series like this, > but if you ask me, I would dare to apply it still. I disagree. Even though the patch series just touches Config.in so is less risky, I think it's a bad idea to still apply it to master now. I wouldn't like to have to release a 2014.02.1 again... Also note that this is not a regression - we've lived with the incompatible kernel headers situation for years. I think that not fixing this behaviour in 2014.02 is less bad than running the risk of breaking something that works. Regards, Arnout -- Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F