From: Michal Marek <mmarek@suse.cz>
To: Valentin Rothberg <valentinrothberg@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
hengelein Stefan <stefan.hengelein@fau.de>,
linux-kernel@vger.kernel.org, Paul Bolle <pebolle@tiscali.nl>
Subject: Re: [PATCH v2] scripts/checkkconfigsymbols.py: support default statements
Date: Mon, 24 Aug 2015 16:57:13 +0200 [thread overview]
Message-ID: <55DB30C9.8070701@suse.cz> (raw)
In-Reply-To: <CAD3Xx4LZpkMTGGCsomecdduszrpcRsJRgaK_KuiWiVC4cugc5Q@mail.gmail.com>
On 2015-08-24 16:52, Valentin Rothberg wrote:
> Hi Michal,
>
> On Mon, Aug 24, 2015 at 4:49 PM, Michal Marek <mmarek@suse.cz> wrote:
>> On 2015-07-27 12:33, Valentin Rothberg wrote:
>>> Until now, checkkonfigsymbols.py did not check default statements for
>>> references on missing Kconfig symbols (i.e., undefined Kconfig options).
>>> Hence, add support to parse and check the Kconfig default statement.
>>>
>>> Signed-off-by: Valentin Rothberg <valentinrothberg@gmail.com>
>>> ---
>>> Changelog:
>>> v2 (thanks to Stefan Hengelein):
>>> - update NUMERIC regex (Kconfig accepts 'X' and 'A-F')
>>> - remove mistakenly added blank line from v1
>>>
>>> scripts/checkkconfigsymbols.py | 9 +++++++--
>>> 1 file changed, 7 insertions(+), 2 deletions(-)
>>
>> Applied to kbuild.git#kconfig.
>>
>> Michal
>>
>
> The patch above already went through Greg's tree to linux-next (see
> commit 0bd38ae35522).
Thanks for the information. I'll undo the change in my tree (I haven't
pushed yet).
Michal
prev parent reply other threads:[~2015-08-24 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-25 14:11 [PATCH] scripts/checkkconfigsymbols.py: support default statements Valentin Rothberg
2015-07-27 10:33 ` [PATCH v2] " Valentin Rothberg
2015-08-24 14:49 ` Michal Marek
2015-08-24 14:52 ` Valentin Rothberg
2015-08-24 14:57 ` Michal Marek [this message]
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=55DB30C9.8070701@suse.cz \
--to=mmarek@suse.cz \
--cc=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