public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Poirier <bpoirier@suse.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Michal Marek <mmarek@suse.cz>, joeyli <jlee@suse.com>,
	"Yann E . MORIN " <yann.morin.1998@free.fr>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] localmodconfig: Fix whitespace repeat count after "tristate"
Date: Tue, 26 Apr 2016 14:35:19 -0700	[thread overview]
Message-ID: <20160426213519.GA4812@f1.synalogic.ca> (raw)
In-Reply-To: <20160426155132.3cdf9adf@gandalf.local.home>

On 2016/04/26 15:51, Steven Rostedt wrote:
> On Tue, 26 Apr 2016 11:56:38 -0700
> Benjamin Poirier <bpoirier@suse.com> wrote:
> 
> > Also recognize standalone "prompt".
> > 
> > Before this patch we incorrectly identified some symbols as not having a
> > prompt and potentially needing to be selected by something else.
> > 
> > Note that this patch could theoretically change the resulting .config,
> > causing it to have fewer symbols turned on. However, given the current set
> > of Kconfig files, this situation does not occur because the symbols newly
> > added to %prompts are absent from %selects.
> > 
> > Signed-off-by: Benjamin Poirier <bpoirier@suse.com>
> > ---
> >  scripts/kconfig/streamline_config.pl | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/scripts/kconfig/streamline_config.pl b/scripts/kconfig/streamline_config.pl
> > index 95a6f2b..b8c7b29 100755
> > --- a/scripts/kconfig/streamline_config.pl
> > +++ b/scripts/kconfig/streamline_config.pl
> > @@ -237,7 +237,7 @@ sub read_kconfig {
> >  	    }
> >  
> >  	# configs without prompts must be selected
> > -	} elsif ($state ne "NONE" && /^\s*tristate\s\S/) {
> > +	} elsif ($state ne "NONE" && /^\s*(tristate\s+\S|prompt\b)/) {
> 
> I prefer not to have the "prompt" here. I'm only interested in module
> configs. But the \s to \s+ is a real fix.

Separate tristate and prompt statements are allowed and recognized by
the kconfig parser. Although there are no such cases now, there used to
be one: 0a57274
You sure you want to remove it from the regexp?

  reply	other threads:[~2016-04-26 21:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-02 17:55 [PATCH 1/2] localmodconfig: Fix parsing of Kconfig "source" statements Benjamin Poirier
2016-04-02 17:55 ` [PATCH 2/2] localmodconfig: Reset certificate paths Benjamin Poirier
2016-04-08 14:59   ` joeyli
2016-04-26 14:02   ` Steven Rostedt
2016-04-26 18:51     ` Benjamin Poirier
2016-04-26 18:52       ` [PATCH v2] " Benjamin Poirier
2016-04-26 19:48         ` Steven Rostedt
2016-04-08 14:59 ` [PATCH 1/2] localmodconfig: Fix parsing of Kconfig "source" statements joeyli
2016-04-26 14:03   ` Steven Rostedt
2016-04-08 18:29 ` Steven Rostedt
2016-04-10 23:52   ` Benjamin Poirier
2016-04-11  0:06     ` [PATCH 1/4] localmodconfig: Recognize more keywords that end a menu entry Benjamin Poirier
2016-04-11  0:06       ` [PATCH 2/4] localmodconfig: Fix parsing of "help" text Benjamin Poirier
2016-04-11  0:06       ` [PATCH 3/4] localmodconfig: Add missing $ to reference a variable Benjamin Poirier
2016-04-11  0:06       ` [PATCH 4/4] localmodconfig: Recognize standalone "prompt" Benjamin Poirier
2016-04-26 15:11         ` Steven Rostedt
2016-04-26 18:54           ` Benjamin Poirier
2016-04-26 18:56             ` [PATCH v2] localmodconfig: Fix whitespace repeat count after "tristate" Benjamin Poirier
2016-04-26 19:51               ` Steven Rostedt
2016-04-26 21:35                 ` Benjamin Poirier [this message]
2016-04-26 22:34                   ` Steven Rostedt
2016-04-18 20:29     ` [PATCH 1/2] localmodconfig: Fix parsing of Kconfig "source" statements Benjamin Poirier
2016-04-18 21:43       ` Steven Rostedt
2016-04-18 23:49         ` Benjamin Poirier

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=20160426213519.GA4812@f1.synalogic.ca \
    --to=bpoirier@suse.com \
    --cc=jlee@suse.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=rostedt@goodmis.org \
    --cc=yann.morin.1998@free.fr \
    /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