mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Valentin Rothberg <Valentin.Rothberg@lip6.fr>
Cc: gregkh@linuxfoundation.org, stefan.hengelein@fau.de,
	linux-kernel@vger.kernel.org, rupran@einserver.de
Subject: Re: [PATCH] checkkconfigsymbols.py: filter reports for tools/
Date: Tue, 03 Mar 2015 01:57:08 +0100	[thread overview]
Message-ID: <1425344228.24292.140.camel@x220> (raw)
In-Reply-To: <1424873723-6311-1-git-send-email-Valentin.Rothberg@lip6.fr>

On Wed, 2015-02-25 at 15:15 +0100, Valentin Rothberg wrote:
> @@ -46,8 +46,9 @@ def main():
>          stdout = stdout[:-1]
>  
>      for gitfile in stdout.rsplit("\n"):
> -        if ".git" in gitfile or "ChangeLog" in gitfile or \
> -                ".log" in gitfile or os.path.isdir(gitfile):
> +        if ".git" in gitfile or "ChangeLog" in gitfile or      \
> +                ".log" in gitfile or os.path.isdir(gitfile) or \
> +                gitfile.startswith("tools/"):

Perhaps just
    gitfile == "tools/perf/config/Makefile"

(but I'm unsure if that's valid python)? 

>              continue
>          if REGEX_FILE_KCONFIG.match(gitfile):
>              kconfig_files.append(gitfile)

This patch was triggered by perf changes that hit next-20150225, wasn't
it? If so, we might want to find out why the perf people need to use
their
    "$(call detected,CONFIG_EXAMPLE)"

hack. Especially because that hack is also used on existing Kconfig
symbols (I spotted X86, X86_64, AUDIT, and NUMA). And the usage of both
valid Kconfig macros and faux Kconfig macros in that hack looks odd to
me.


Paul Bolle


  reply	other threads:[~2015-03-03  0:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-25 14:15 Valentin Rothberg
2015-03-03  0:57 ` Paul Bolle [this message]
2015-03-03  7:55   ` Valentin Rothberg
2015-03-03 22:52     ` Paul Bolle

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=1425344228.24292.140.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=Valentin.Rothberg@lip6.fr \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rupran@einserver.de \
    --cc=stefan.hengelein@fau.de \
    /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

all inboxes | Powered by JetHome®