public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Olof Johansson <olof@lixom.net>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Russell King <linux@arm.linux.org.uk>,
	Laura Abbott <laura@labbott.name>
Subject: Re: [RFC PATCH 00/23] arm: defconfigs: use kconfig fragments
Date: Wed, 07 Dec 2016 22:35:42 +0100	[thread overview]
Message-ID: <2155947.mOKhpZPiAn@wuerfel> (raw)
In-Reply-To: <CAOesGMi_mLG+tS0Ya8G9KLO_sUYGtLmgcvFfpn0Nwbd-KMKOrQ@mail.gmail.com>

On Wednesday, December 7, 2016 1:14:02 PM CET Olof Johansson wrote:
> >
> > - A "debug" fragment would be nice, to turn on common options that
> >   add a lot of useful runtime checks at the expense of performance
> >   or code size.
> 
> Hmm, some of these might work but several useful debug options (in
> particular DEBUG_LL for early errors) are per-system/platform.

I was thinking mostly of architecture-independent options, i.e.
the stuff that is in lib/Kconfig.debug but isn't too expensive
to be run in a regular test environment. Enabling those
for a build/boot automation environment would be particularly
useful as you'd catch more bugs that get introduced through
a random patch.

> > - A "distro" fragment that turns on all loadable modules that are
> >   enabled by common distributions (e.g. two or more of
> >   debian/fedora/opensuse/gentoo), to let you build a drop-in
> >   replacement kernel for a shipping distro. This would also allow
> >   the distros to strip their own config files and just specify
> >   whatever differs from the others.
> 
> Keeping this in sync with the distro kernel could be a bit awkward
> (and possibly churny).

It would certainly need buy-in from distro maintainers. I've discussed
this with Laura Abbott in the past, and she was interested in
principle.

	Arnd

  reply	other threads:[~2016-12-07 21:36 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-06 12:38 [RFC PATCH 00/23] arm: defconfigs: use kconfig fragments Bartlomiej Zolnierkiewicz
2016-12-06 12:38 ` [RFC PATCH 01/23] arm: add kconfig fragments support Bartlomiej Zolnierkiewicz
2016-12-06 12:38 ` [RFC PATCH 02/23] arm: use kconfig fragments for ARCH_ASPEED defconfigs Bartlomiej Zolnierkiewicz
2016-12-06 12:38 ` [RFC PATCH 03/23] arm: update defconfigs for ARCH_KS8695 Bartlomiej Zolnierkiewicz
2016-12-06 12:38 ` [RFC PATCH 04/23] arm: use kconfig fragments for ARCH_ASPEED defconfigs Bartlomiej Zolnierkiewicz
2016-12-06 13:22   ` Baruch Siach
2016-12-06 12:38 ` [RFC PATCH 05/23] arm: update defconfigs for ARCH_MMP Bartlomiej Zolnierkiewicz
2016-12-06 12:38 ` [RFC PATCH 06/23] arm: use kconfig fragments for ARCH_ASPEED defconfigs Bartlomiej Zolnierkiewicz
2016-12-06 12:38 ` [RFC PATCH 07/23] arm: update defconfigs for PLAT_SPEAR Bartlomiej Zolnierkiewicz
2016-12-06 12:38 ` [RFC PATCH 08/23] arm: use kconfig fragments for PLAT_SPEAR defconfigs Bartlomiej Zolnierkiewicz
2016-12-06 12:38 ` [RFC PATCH 09/23] arm: update defconfigs for ARCH_W90X900 Bartlomiej Zolnierkiewicz
2016-12-06 12:38 ` [RFC PATCH 10/23] arm: use kconfig fragments for ARCH_W90X900 defconfigs Bartlomiej Zolnierkiewicz
2016-12-06 12:38 ` [RFC PATCH 11/23] arm: update mainstone_defconfig Bartlomiej Zolnierkiewicz
2016-12-06 12:38 ` [RFC PATCH 12/23] arm: update lubbock_defconfig Bartlomiej Zolnierkiewicz
2016-12-06 12:38 ` [RFC PATCH 13/23] arm: update pxa255-idp_defconfig Bartlomiej Zolnierkiewicz
2016-12-06 12:38 ` [RFC PATCH 14/23] arm: update lpd270_defconfig Bartlomiej Zolnierkiewicz
2016-12-06 12:38 ` [RFC PATCH 15/23] arm: use kconfig fragments for ARCH_PXA defconfigs (part 1) Bartlomiej Zolnierkiewicz
2016-12-10  9:46   ` Robert Jarzmik
2016-12-12 12:11     ` Bartlomiej Zolnierkiewicz
2016-12-06 12:38 ` [RFC PATCH 16/23] arm: update corgi_defconfig Bartlomiej Zolnierkiewicz
2016-12-06 12:38 ` [RFC PATCH 17/23] arm: update spitz_defconfig Bartlomiej Zolnierkiewicz
2016-12-06 12:38 ` [RFC PATCH 18/23] arm: use kconfig fragments for ARCH_PXA defconfigs (part 2) Bartlomiej Zolnierkiewicz
2016-12-06 12:38 ` [RFC PATCH 19/23] arm: update ezx_defconfig Bartlomiej Zolnierkiewicz
2016-12-06 12:38 ` [RFC PATCH 20/23] arm: imote2_defconfig Bartlomiej Zolnierkiewicz
2016-12-06 12:38 ` [RFC PATCH 21/23] arm: use kconfig fragments for ARCH_PXA defconfigs (part 3) Bartlomiej Zolnierkiewicz
2016-12-06 19:03 ` [RFC PATCH 00/23] arm: defconfigs: use kconfig fragments Olof Johansson
2016-12-07 11:41   ` Bartlomiej Zolnierkiewicz
2016-12-07 21:07     ` Arnd Bergmann
2016-12-07 21:14       ` Olof Johansson
2016-12-07 21:35         ` Arnd Bergmann [this message]
2016-12-07 21:56           ` Laura Abbott
2016-12-07 22:21             ` Olof Johansson
     [not found] ` <1481027938-31831-24-git-send-email-b.zolnierkie@samsung.com>
2016-12-06 19:49   ` [RFC PATCH 23/23] arm: use kconfig fragments for tegra_defconfig/multi_v7_defconfig Olof Johansson
2016-12-13  8:08 ` [RFC PATCH 00/23] arm: defconfigs: use kconfig fragments Uwe Kleine-König

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=2155947.mOKhpZPiAn@wuerfel \
    --to=arnd@arndb.de \
    --cc=b.zolnierkie@samsung.com \
    --cc=laura@labbott.name \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=olof@lixom.net \
    /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