From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933043Ab3GLMGU (ORCPT ); Fri, 12 Jul 2013 08:06:20 -0400 Received: from mail-ee0-f47.google.com ([74.125.83.47]:43348 "EHLO mail-ee0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932887Ab3GLMGS (ORCPT ); Fri, 12 Jul 2013 08:06:18 -0400 Date: Fri, 12 Jul 2013 14:06:13 +0200 From: Ingo Molnar To: Andrew Morton Cc: Borislav Petkov , Kyungsik Lee , Michal Marek , linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org, x86@kernel.org, celinux-dev@lists.celinuxforum.org, linux-arm-kernel@lists.infradead.org, hyojun.im@lge.com, chan.jeong@lge.com, raphael.andy.lee@gmail.com, "H. Peter Anvin" , Ingo Molnar , Thomas Gleixner , Russell King , Florian Fainelli , Yann Collet , Chanho Min , Linus Torvalds Subject: Re: [PATCH -next 2/2] kbuild: fix for updated LZ4 tool with the new streaming format Message-ID: <20130712120613.GA21313@gmail.com> References: <1367829775-4434-1-git-send-email-kyungsik.lee@lge.com> <1367829775-4434-2-git-send-email-kyungsik.lee@lge.com> <20130712075602.GA4002@gmail.com> <20130712080145.GC24008@pd.tnic> <20130712101319.GA13421@gmail.com> <20130712102326.GE24008@pd.tnic> <20130712041810.53c86e5f.akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130712041810.53c86e5f.akpm@linux-foundation.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Andrew Morton wrote: > On Fri, 12 Jul 2013 12:23:26 +0200 Borislav Petkov wrote: > > > On Fri, Jul 12, 2013 at 12:13:19PM +0200, Ingo Molnar wrote: > > > and now it is upstream already, via -mm: > > > > > > e76e1fdfa8f8 lib: add support for LZ4-compressed kernel > > > > Sure. Let's see if it manages to get released b0rked like it is right > > now. > > Well y'know, if whining fixed bugs then there would be no problem here > at all. > > This problem came up briefly and I thought it had been adequately > addressed. Now a month or two later we find out who are the people who > can't be bothered testing -next, but think it terribly important that > others do so. At least with my limited resources -next is unusable for my randconfig testing. I can randconfig test the fresh new bugs I introduce plus the bugs that slip upstream - which naturally peak during the merge window. Anyway, I hacked it around locally, sh*t happens, it should be easy enough to fix. Thanks, Ingo From mboxrd@z Thu Jan 1 00:00:00 1970 From: mingo@kernel.org (Ingo Molnar) Date: Fri, 12 Jul 2013 14:06:13 +0200 Subject: [PATCH -next 2/2] kbuild: fix for updated LZ4 tool with the new streaming format In-Reply-To: <20130712041810.53c86e5f.akpm@linux-foundation.org> References: <1367829775-4434-1-git-send-email-kyungsik.lee@lge.com> <1367829775-4434-2-git-send-email-kyungsik.lee@lge.com> <20130712075602.GA4002@gmail.com> <20130712080145.GC24008@pd.tnic> <20130712101319.GA13421@gmail.com> <20130712102326.GE24008@pd.tnic> <20130712041810.53c86e5f.akpm@linux-foundation.org> Message-ID: <20130712120613.GA21313@gmail.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Andrew Morton wrote: > On Fri, 12 Jul 2013 12:23:26 +0200 Borislav Petkov wrote: > > > On Fri, Jul 12, 2013 at 12:13:19PM +0200, Ingo Molnar wrote: > > > and now it is upstream already, via -mm: > > > > > > e76e1fdfa8f8 lib: add support for LZ4-compressed kernel > > > > Sure. Let's see if it manages to get released b0rked like it is right > > now. > > Well y'know, if whining fixed bugs then there would be no problem here > at all. > > This problem came up briefly and I thought it had been adequately > addressed. Now a month or two later we find out who are the people who > can't be bothered testing -next, but think it terribly important that > others do so. At least with my limited resources -next is unusable for my randconfig testing. I can randconfig test the fresh new bugs I introduce plus the bugs that slip upstream - which naturally peak during the merge window. Anyway, I hacked it around locally, sh*t happens, it should be easy enough to fix. Thanks, Ingo