From: Paul Bolle <pebolle@tiscali.nl>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Valentin Rothberg <valentinrothberg@gmail.com>,
stefan.hengelein@fau.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkkconfigsymbols.py: add option -i to ignore files
Date: Fri, 01 May 2015 22:30:35 +0200 [thread overview]
Message-ID: <1430512235.3928.34.camel@tiscali.nl> (raw)
In-Reply-To: <20150501194532.GA523@kroah.com>
Greg KH schreef op vr 01-05-2015 om 21:45 [+0200]:
> On Fri, May 01, 2015 at 09:31:36PM +0200, Paul Bolle wrote:
> > Patch hijack: it's been my view for some time now that almost all
> > defconfigs are outdated in one way or another. And they are outdated
> > because they are not, as far as I can tell, updated regularly. So I
> > wonder whether there are any guidelines for defconfigs. What is their
> > purpose? What exactly can one expect when using a defconfig?
>
> When ever I bring this up, someone says, "but we need it to define how
> to select the options for my arch / board!" How real this is is really
> unknown to me but the arches other than x86 seem to insist that they are
> relevant.
Perhaps I should, just for fun, rebuild v4.1-rc1 using a x86 defconfig
and see what happens. Note that I'm typing this on v4.1-rc1 using an
x86 .config based on what Fedora ships for 21 (which is, on its turn,
based on 3.19.5).
Paul Bolle
next prev parent reply other threads:[~2015-05-01 20:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 14:58 [PATCH] checkkconfigsymbols.py: add option -i to ignore files Valentin Rothberg
2015-05-01 19:31 ` Paul Bolle
2015-05-01 19:45 ` Greg KH
2015-05-01 20:30 ` Paul Bolle [this message]
2015-05-01 20:45 ` Greg KH
2015-05-01 20:13 ` Valentin Rothberg
2015-05-01 20:49 ` Paul Bolle
2015-05-01 21:04 ` Valentin Rothberg
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=1430512235.3928.34.camel@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefan.hengelein@fau.de \
--cc=valentinrothberg@gmail.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