Linux kbuild/kconfig development
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Chris Brandt <Chris.Brandt@renesas.com>
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Greg Ungerer <gerg@linux-m68k.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Vladimir Murzin <vladimir.murzin@arm.com>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCHv4 4/4] ARM: versatile: support configuring versatile machine for no-MMU
Date: Fri, 22 Jun 2018 19:38:38 +0100	[thread overview]
Message-ID: <20180622183838.GZ17671@n2100.armlinux.org.uk> (raw)
In-Reply-To: <TY1PR01MB1562C54E8DD3942F40F8CBBD8A750@TY1PR01MB1562.jpnprd01.prod.outlook.com>

On Fri, Jun 22, 2018 at 05:23:09PM +0000, Chris Brandt wrote:
> Then here's a question.
> 
> To be clear, the discussion is around
> 
>   "Being able to build a kernel that will not boot"
> 
> So which one of these is more important: build or boot?

We care about both.

> Meaning what if you can select multiple platforms in kconfig, but then 
> there is a .c file that does more sanity checking that then prevents the 
> full build using a #error.

... which is not acceptable.  We have a lot of automated build
infrastructure to build almost every commit in the mainline kernel
against almost every build configuration that is present in the
kernel and every architecture that is present in the mainline kernel.
We also have people that build random configurations and fix any
build failures and warnings which result from that.

I also build randconfigs here.

> In that case you can never "build" a kernel that has no chance of 
> booting on all the selected platforms.
> 
> There are configs options today that you can select, but unless some 
> external criteria is  met during build time, the build will fail (like
> with a "missing .h file" message or something)

Such as?  I don't think that's found by the randconfig builders - I've
never noticed any such failures on ARM.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 8.8Mbps down 630kbps up
According to speedtest.net: 8.21Mbps down 510kbps up

  parent reply	other threads:[~2018-06-22 18:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180618141905.7789-1-gerg@linux-m68k.org>
     [not found] ` <20180618141905.7789-5-gerg@linux-m68k.org>
     [not found]   ` <CAMuHMdUyCEq0U_CJindwcSEF+0dR-SJc1v8zGT-CcUqVkdOeVw@mail.gmail.com>
2018-06-21 16:24     ` [PATCHv4 4/4] ARM: versatile: support configuring versatile machine for no-MMU Nicolas Pitre
2018-06-21 16:45       ` Chris Brandt
2018-06-22  6:27         ` Geert Uytterhoeven
2018-06-22 13:26           ` Chris Brandt
2018-06-22 11:01       ` Russell King - ARM Linux
2018-06-22 15:25         ` Nicolas Pitre
2018-06-22 15:33           ` Geert Uytterhoeven
2018-06-22 15:57             ` Nicolas Pitre
2018-06-22 16:11               ` Russell King - ARM Linux
2018-06-22 16:21                 ` Nicolas Pitre
2018-06-22 16:40                   ` Russell King - ARM Linux
2018-06-22 16:54                     ` Nicolas Pitre
2018-06-22 17:09                       ` Russell King - ARM Linux
2018-06-22 17:25                         ` Nicolas Pitre
2018-06-22 16:40                 ` Chris Brandt
2018-06-22 16:44               ` Chris Brandt
2018-06-22 17:05                 ` Nicolas Pitre
2018-06-22 17:23                   ` Chris Brandt
2018-06-22 17:47                     ` Nicolas Pitre
2018-06-22 18:38                     ` Russell King - ARM Linux [this message]
2018-06-22 20:25                       ` Chris Brandt
2018-06-22 20:28                         ` Geert Uytterhoeven
2018-06-22 20:33                         ` Russell King - ARM Linux

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=20180622183838.GZ17671@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=Chris.Brandt@renesas.com \
    --cc=arnd@arndb.de \
    --cc=geert@linux-m68k.org \
    --cc=gerg@linux-m68k.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=nicolas.pitre@linaro.org \
    --cc=vladimir.murzin@arm.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox