From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752463AbcF0VIe (ORCPT ); Mon, 27 Jun 2016 17:08:34 -0400 Received: from mout.kundenserver.de ([217.72.192.73]:55459 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752295AbcF0VIb (ORCPT ); Mon, 27 Jun 2016 17:08:31 -0400 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: Kevin Hilman , "kernelci. org bot" , linux-kernel@vger.kernel.org, kernel-build-reports@lists.linaro.org Subject: Re: next build: 142 builds: 6 failed, 136 passed, 17 errors, 111 warnings (next-20160624) Date: Mon, 27 Jun 2016 23:10:38 +0200 Message-ID: <3959952.E4k8LWTObD@wuerfel> User-Agent: KMail/5.1.3 (Linux/4.4.0-22-generic; KDE/5.18.0; x86_64; ; ) In-Reply-To: References: <576da61b.4d9a1c0a.d5671.1807@mx.google.com> <6046594.ORRxUGPcVO@wuerfel> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:yFww1CagT6RS7PKOT8JjKX6KvnFDv0GXqyd1M1sI0DODrAHDx64 KL7o40OjJfYN9tfjSq0sIYggTDAlVqGyXIGWejhTz9Nt3qGdEs0YFSVggPHDsmd7TopiKqk 0iMxjcYAMZ7FVuqILzCOFuoqNa2j+yL7Ot43NawOP0zPHaXzfkdWekjUGBom3ozV0h9gRL2 Gcs3mUL7VTPK5FptSLl3w== X-UI-Out-Filterresults: notjunk:1;V01:K0:BGleLXeWpHY=:1Xc5VgtEqj61pDrSKeIbJz hWi5P77+15jS4cVYN73LheO1F6Dpqz09yMNXYyiBM/pW50CGQOo9W/rdAbcmb+eLIzW2aVKcY ih5EflNUBR//FRO8zK3n2VmaKPvBT3BDpVu8w1ToH5fL0hoYvABPkIlaV4k7H8j0lFmMN2DSs PwSfTvRdGWl2W1+a2A7ssdoJxLrUGS5UAAdCydxf2bYcUTUFwGgfQAU60KyTQo8TEftEr80l7 Fz2/ie1M7BwsZIIo7dySMqvRu6QiLe4wZeNUmvMTO1BSoJnKLW96RUDGNSRa+Cy43u1QA4XVF S3A0EHYLemIa3JW7bmLz/4aVVwDIE3Y4A+XJpdVfWWFjdtblZTbQro2LjCDM5jY2pIY2yRV4p 1E1DaixFhtGLtVGi03IM+0hu6mJxITWPDgIiL7z4Fuoe3T7cmCGapLBEzxPyuGqdsDphCPUgh x4NW0ejinRGWG+bK5q4ijvzG3qZj1wZw+CGD1pZF/bnuKzTvCf9rhuODZn4y2a14qLXHlI8Dz Rcqwf5UXLghtWFnQKgGkFybIxOGc9j+onRr8l+5G8AUYbemHBXaiNvCsl+wMylZEi0sLbf6sQ DzAvxCMyfc0wroksRpmrkFJPlO3MOlmV07a7jaytVx4RpjPBWkFD27CIDWm6y7M2bSLOOFASQ KwbJZ2/7vYbMLFWEB4q65MslhCHjSshWzVBF4fIpDNSDtN6/ep2IVRtdol4QT1CsAXFKJIkjo yinhJjfgEB4jOjk1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Monday, June 27, 2016 1:30:17 PM CEST Kevin Hilman wrote: > Arnd Bergmann writes: > > > On Friday, June 24, 2016 2:28:59 PM CEST kernelci. org bot wrote: > > [...] > > >> 1 .config:972:warning: override: NOHIGHMEM changes choice state > >> 1 .config:971:warning: override: SLOB changes choice state > >> 1 .config:969:warning: override: KERNEL_XZ changes choice state > >> 1 .config:968:warning: override: CC_OPTIMIZE_FOR_SIZE changes choice state > >> 1 .config:944:warning: override: SLOB changes choice state > >> 1 .config:941:warning: override: CC_OPTIMIZE_FOR_SIZE changes choice state > >> 1 .config:877:warning: override: SLOB changes choice state > >> 1 .config:875:warning: override: KERNEL_XZ changes choice state > >> 1 .config:874:warning: override: CC_OPTIMIZE_FOR_SIZE changes choice state > > > > The tinyconfig warnings are really annoying > > > > Hmm, yeah. We should probably just filter out all the kconfig warnings > that happen when we use config fragments, since the point of the > fragment is to override things and change state. > > Right now, our check for warnings is a rather simple grep, but I'll add > this to the TODO list. I've looked at this before and sadly, the scripts/kconfig tool can do it right if you pass in both the base config file (defconfig, or flag for allnoconfig/allmod/...) *and* the fragment, but the way that the Makefile works for minconfig is that we first generate a .config file and then add the fragment for minconfig to that, and this causes the warnings above. This should be fixable by patching the kernel Makefiles, but I have not come up with a nice way to do that. Arnd From mboxrd@z Thu Jan 1 00:00:00 1970 From: arnd@arndb.de (Arnd Bergmann) Date: Mon, 27 Jun 2016 23:10:38 +0200 Subject: next build: 142 builds: 6 failed, 136 passed, 17 errors, 111 warnings (next-20160624) In-Reply-To: References: <576da61b.4d9a1c0a.d5671.1807@mx.google.com> <6046594.ORRxUGPcVO@wuerfel> Message-ID: <3959952.E4k8LWTObD@wuerfel> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Monday, June 27, 2016 1:30:17 PM CEST Kevin Hilman wrote: > Arnd Bergmann writes: > > > On Friday, June 24, 2016 2:28:59 PM CEST kernelci. org bot wrote: > > [...] > > >> 1 .config:972:warning: override: NOHIGHMEM changes choice state > >> 1 .config:971:warning: override: SLOB changes choice state > >> 1 .config:969:warning: override: KERNEL_XZ changes choice state > >> 1 .config:968:warning: override: CC_OPTIMIZE_FOR_SIZE changes choice state > >> 1 .config:944:warning: override: SLOB changes choice state > >> 1 .config:941:warning: override: CC_OPTIMIZE_FOR_SIZE changes choice state > >> 1 .config:877:warning: override: SLOB changes choice state > >> 1 .config:875:warning: override: KERNEL_XZ changes choice state > >> 1 .config:874:warning: override: CC_OPTIMIZE_FOR_SIZE changes choice state > > > > The tinyconfig warnings are really annoying > > > > Hmm, yeah. We should probably just filter out all the kconfig warnings > that happen when we use config fragments, since the point of the > fragment is to override things and change state. > > Right now, our check for warnings is a rather simple grep, but I'll add > this to the TODO list. I've looked at this before and sadly, the scripts/kconfig tool can do it right if you pass in both the base config file (defconfig, or flag for allnoconfig/allmod/...) *and* the fragment, but the way that the Makefile works for minconfig is that we first generate a .config file and then add the fragment for minconfig to that, and this causes the warnings above. This should be fixable by patching the kernel Makefiles, but I have not come up with a nice way to do that. Arnd