Date: Fri, 1 May 2015 21:45:32 +0200
From: Greg KH <gregkh@linuxfoundation.org>
To: Paul Bolle <pebolle@tiscali.nl>
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
Message-ID: <20150501194532.GA523@kroah.com>
References: <1430319507-1869-1-git-send-email-valentinrothberg@gmail.com>
 <1430508696.3928.27.camel@tiscali.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1430508696.3928.27.camel@tiscali.nl>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1213
Lines: 29

On Fri, May 01, 2015 at 09:31:36PM +0200, Paul Bolle wrote:
> Valentin Rothberg schreef op wo 29-04-2015 om 16:58 [+0200]:
> > Sometimes a user might be interested to filter certain reports (e.g.,
> > the many defconfigs).
> 
> Is this actually useful outside of filtering out defconfigs?
> 
> > Now, this can be achieved by specifying a Python
> > regex with -i / --ignore.
> 
> 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.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/