public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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
Date: Fri, 1 May 2015 21:45:32 +0200	[thread overview]
Message-ID: <20150501194532.GA523@kroah.com> (raw)
In-Reply-To: <1430508696.3928.27.camel@tiscali.nl>

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

  reply	other threads:[~2015-05-01 19:45 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 [this message]
2015-05-01 20:30     ` Paul Bolle
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=20150501194532.GA523@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --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