All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kernel-build-reports@lists.linaro.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"kernelci. org bot" <bot@kernelci.org>
Subject: Re: next build: 142 builds: 6 failed, 136 passed, 17 errors, 111 warnings (next-20160624)
Date: Mon, 27 Jun 2016 13:30:17 -0700	[thread overview]
Message-ID: <m2ziq6s7c6.fsf@baylibre.com> (raw)
In-Reply-To: <6046594.ORRxUGPcVO@wuerfel> (Arnd Bergmann's message of "Mon, 27 Jun 2016 13:37:23 +0200")

Arnd Bergmann <arnd@arndb.de> 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.

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: next build: 142 builds: 6 failed, 136 passed, 17 errors, 111 warnings (next-20160624)
Date: Mon, 27 Jun 2016 13:30:17 -0700	[thread overview]
Message-ID: <m2ziq6s7c6.fsf@baylibre.com> (raw)
In-Reply-To: <6046594.ORRxUGPcVO@wuerfel> (Arnd Bergmann's message of "Mon, 27 Jun 2016 13:37:23 +0200")

Arnd Bergmann <arnd@arndb.de> 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.

Kevin

  reply	other threads:[~2016-06-27 20:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <576da61b.4d9a1c0a.d5671.1807@mx.google.com>
2016-06-27 11:37 ` next build: 142 builds: 6 failed, 136 passed, 17 errors, 111 warnings (next-20160624) Arnd Bergmann
2016-06-27 11:37   ` Arnd Bergmann
2016-06-27 20:30   ` Kevin Hilman [this message]
2016-06-27 20:30     ` Kevin Hilman
2016-06-27 21:10     ` Arnd Bergmann
2016-06-27 21:10       ` Arnd Bergmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2ziq6s7c6.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=arnd@arndb.de \
    --cc=bot@kernelci.org \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.