public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Russell King <linux@arm.linux.org.uk>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/3] Include kernel config by default
Date: Sun, 27 Jan 2013 17:28:52 +0100	[thread overview]
Message-ID: <510555C4.4020502@ahsoftware.de> (raw)
In-Reply-To: <1359207268-9340-1-git-send-email-holler@ahsoftware.de>

Am 26.01.2013 14:34, schrieb Alexander Holler:
> Hello,
>
> I've seen too many systems where the config to build the used kernel got
> lost and people were unable to diagnose problems or to rebuild a modified
> or updated kernel. It's a subject which worries me since several years.
>
> Therefor I finally prepared the following patch(es) to include the config
> by default, make it by default accessible through /proc/config.gz, to
> hide the option to not include the config below "embedded" and to remove all
> now unnecessary IKCONFIG_* options from 174 defconfigs (almost all of them
> enabled those options explicit).
>
> I've already posted that two times before
> (https://lkml.org/lkml/2012/7/25/2 and https://lkml.org/lkml/2012/10/18/132)
> without even getting a single response. So I don't know if it's a totally
> foolish idea, if nobody is interested, or if the previous patches just weren't
> seen by anybody.
>
> I've now added the maintainers of the two large architectures (x86 and arm), the
> master himself and a few other people to cc (sorry if I've missed any important
> person), and I made the subject more clearly.
>
> Maybe this will provoke at least a single response. ;)

To add a last note:

I really only care about the first patch which sets the default to y. 
The other two patches are more or less "nice to have" (imho) and the 
third patch could be even splitted into 14 patches (one for every 
architecture) or even 174 singles patches (one for every board(-type). 
If requested I would split the third patch.

But now I'm finished. ;) So if no one responses (or feels responsible), 
I won't bother again through sending them again.

Regards,

Alexander

      parent reply	other threads:[~2013-01-27 16:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-26 13:34 [PATCH 0/3] Include kernel config by default Alexander Holler
2013-01-26 13:34 ` [PATCH 1/3] " Alexander Holler
2013-01-26 13:34 ` [PATCH 2/3] Show option to not include kernel configuration only for embedded systems Alexander Holler
2013-01-26 13:34 ` [PATCH 3/3] Remove IKCONFIG_* from all defconfigs as those options are now enabled by default Alexander Holler
2013-01-27  4:01 ` [PATCH 0/3] Include kernel config " Andreas Mohr
2013-01-27 16:28 ` Alexander Holler [this message]

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=510555C4.4020502@ahsoftware.de \
    --to=holler@ahsoftware.de \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --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