linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Dave Jones <davej@redhat.com>,
	Greg Kroah-Hartman <greg@kroah.com>,
	Ubuntu Kernel Team <kernel-team@lists.ubuntu.com>,
	Debian Kernel Team <debian-kernel@lists.debian.org>,
	OpenSUSE Kernel Team <opensuse-kernel@opensuse.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Fedora Kernel Team <kernel-team@fedoraproject.org>
Subject: Re: [RFC] Simplifying kernel configuration for distro issues
Date: Thu, 19 Jul 2012 11:45:21 -0400	[thread overview]
Message-ID: <20120719154521.GC8469@zod.bos.redhat.com> (raw)
In-Reply-To: <20120719152618.GD16873@home.goodmis.org>

On Thu, Jul 19, 2012 at 11:26:18AM -0400, Steven Rostedt wrote:
> On Fri, Jul 13, 2012 at 02:17:30PM -0700, Linus Torvalds wrote:
> > 
> > The *two* requirements (and they're really the same theme) I
> > personally think we should have for this are
> > 
> >  -  I think every single "select" for these things should come with a
> > comment about what it is about and why the distro needs it (to show
> > there was some thought involved and not just a blind "took it from the
> > distro config")
> 
> What about expanding on Alan's idea. I'm guessing that 99% of the users
> build the kernel for the box that they are running. If this is the case,
> perhaps we can get the distros to add a:
> 
>   /usr/share/Linux/Kconfig
> 
> And this Kconfig would have something like:
> 
> bool "Distro X config"
>  select A
>  select B
>  select C
>  [...]
> 
> Perhaps with a comment for each select. Or have the comments in the help
> section.
> 
> Then have the kernel kbuild system check if this file exists and include
> it.
> 
> Of course the kbuild system would need to verify that the selects exist,
> and perhaps warn if they do not. But the nice thing about this is that
> you would get the minconfig for the system you are running. When the
> system is updated to a new version, the minconfig would be updated too.
> The list of selects would not have to live in the kernel, nor would the
> kernel need to maintain the list for N+1 different distributions.

Is there a reason you don't want distro maintainers to maintain these
files in the upstream git tree?  (You said "the kernel need to
maintain", but I would expect the distro maintainers to be doing that
work.)

I think it would actually be beneficial to maintain them upstream
instead of in distro kernel packaging.  You'd be able to track the
history of changes with git.  You would see for a given kernel
version what options are set for each distro (e.g. F17 can support
NEW_FOO_THING but F16 userspace can't so it doesn't select that).
Perhaps most importantly, it provides a consolidated view of what
options various distros are setting and allows the distro maintainers to
easily do comparisons.

josh

  parent reply	other threads:[~2012-07-19 15:45 UTC|newest]

Thread overview: 86+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-13 20:37 [RFC] Simplifying kernel configuration for distro issues Linus Torvalds
2012-07-13 20:54 ` Myklebust, Trond
2012-07-13 21:41   ` [opensuse-kernel] " richard -rw- weinberger
2012-07-14 10:37     ` Borislav Petkov
2012-07-14 12:12       ` Pekka Enberg
2012-07-14 12:43         ` Cyrill Gorcunov
2012-07-14 17:48           ` Borislav Petkov
2012-07-14 18:51             ` Cyrill Gorcunov
2012-07-14 19:51               ` david
2012-07-19 14:42             ` Steven Rostedt
2012-07-19 16:48               ` Borislav Petkov
2012-07-19 17:02                 ` Steven Rostedt
2012-07-19 17:34                   ` Borislav Petkov
2012-07-19 17:57                     ` Steven Rostedt
2012-07-19 18:09                       ` Borislav Petkov
2012-07-19 17:06                 ` Linus Torvalds
2012-07-19 17:53                   ` Borislav Petkov
2012-07-19 18:42                     ` Konrad Rzeszutek Wilk
2012-07-15 10:14         ` Borislav Petkov
2012-07-15 10:17           ` Pekka Enberg
2012-07-15 21:18             ` Borislav Petkov
2012-07-15 21:48               ` Cyrill Gorcunov
2012-07-15 22:09                 ` david
2012-07-15 22:22                   ` Cyrill Gorcunov
2012-07-15 23:06                     ` david
2012-07-16  8:24                   ` Borislav Petkov
2012-07-16 16:43                     ` david
2012-07-16 16:50                       ` Linus Torvalds
2012-07-16 19:26                         ` david
2012-07-16 20:56                           ` Linus Torvalds
2012-07-16 22:21                             ` david
2012-07-18  7:04                               ` Ingo Molnar
2012-07-18  8:42                                 ` david
2012-07-18  9:13                                   ` Ingo Molnar
2012-07-17  8:03                             ` Geert Uytterhoeven
2012-07-19 16:01                               ` Michal Marek
2012-07-16 17:01                     ` Alan Cox
2012-07-16 17:05                       ` david
2012-07-13 21:02 ` Dave Jones
2012-07-13 21:17   ` Linus Torvalds
2012-07-13 22:26     ` Josh Boyer
2012-07-19 15:26     ` Steven Rostedt
2012-07-19 15:43       ` Linus Torvalds
2012-07-19 16:12         ` Steven Rostedt
2012-07-19 15:45       ` Josh Boyer [this message]
2012-07-19 16:08         ` Steven Rostedt
2012-07-19 17:19           ` Josh Boyer
2012-07-19 17:30             ` Alan Cox
2012-07-19 17:38               ` Josh Boyer
2012-07-19 21:13               ` Ben Hutchings
2012-07-20  2:44                 ` david
2012-07-19 17:33             ` Steven Rostedt
2012-07-19 17:41               ` Alan Cox
2012-07-19 17:56               ` Josh Boyer
2012-07-19 18:13                 ` Steven Rostedt
2012-07-19 18:36                   ` Josh Boyer
2012-07-19 21:04                     ` david
2012-07-19 22:35                       ` Josh Boyer
2012-07-19 22:49                         ` Steven Rostedt
2012-07-21 20:47                 ` valdis.kletnieks
2012-07-19 18:20             ` Paul Bolle
2012-07-19 18:22               ` Josh Boyer
2012-07-19 18:49                 ` Geert Uytterhoeven
2012-07-19 18:55                   ` Paul Bolle
2012-07-19 21:30                 ` Geert Uytterhoeven
2012-07-13 21:29   ` Geert Uytterhoeven
2012-07-13 21:50   ` Paul Bolle
2012-07-13 21:55     ` Dave Jones
2012-07-13 22:11       ` Tony Luck
2012-07-13 22:20       ` Paul Bolle
2012-07-13 23:07       ` Frank Rowand
2012-07-13 21:06 ` Khalid Aziz
2012-07-13 21:17 ` Casey Schaufler
2012-07-13 21:20   ` Linus Torvalds
2012-07-13 22:13     ` david
2012-07-13 21:59 ` Hans de Bruin
2012-07-13 22:33 ` Jesper Juhl
2012-07-13 22:46   ` david
2012-07-14  9:44   ` Olivier Galibert
2012-07-14  4:18 ` Ben Hutchings
2012-07-14 12:35   ` Josh Boyer
2012-07-19  1:48 ` Steven Yong
2012-07-20  9:47 ` Jiri Kosina
2012-07-20 10:26   ` Sam Ravnborg
  -- strict thread matches above, loose matches on Subject: below --
2012-07-18  9:55 Tom Gundersen
2012-07-22 20:10 ` David Greaves

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=20120719154521.GC8469@zod.bos.redhat.com \
    --to=jwboyer@redhat.com \
    --cc=davej@redhat.com \
    --cc=debian-kernel@lists.debian.org \
    --cc=greg@kroah.com \
    --cc=kernel-team@fedoraproject.org \
    --cc=kernel-team@lists.ubuntu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=opensuse-kernel@opensuse.org \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).