From: Michael Ellerman <mpe@ellerman.id.au>
To: Valentin Rothberg <valentinrothberg@gmail.com>
Cc: Cyril Bur <cyrilbur@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"linuxppc-dev\@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] powerpc: process.c: fix Kconfig typo
Date: Wed, 26 Oct 2016 21:40:37 +1100 [thread overview]
Message-ID: <87y41bwfyy.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <CAD3Xx4KqNbpjognpyC=NVqFQ0wH+uc+vQU23PP99625ufCLZnA@mail.gmail.com>
Valentin Rothberg <valentinrothberg@gmail.com> writes:
> On Wed, Oct 26, 2016 at 7:52 AM, Michael Ellerman <mpe@ellerman.id.au> wrote:
>> Cyril Bur <cyrilbur@gmail.com> writes:
>>
>>> On Wed, 2016-10-05 at 07:57 +0200, Valentin Rothberg wrote:
>>>> s/ALIVEC/ALTIVEC/
>>>>
>>>
>>> Oops, nice catch
>>>
>>>> Signed-off-by: Valentin Rothberg <valentinrothberg@gmail.com>
>>>
>>> Reviewed-by: Cyril Bur <cyrilbur@gmail.com>
>>
>> How did we not notice? Sounds like we need a new selftest.
>>
>> Looks like this should have:
>>
>> Fixes: dc16b553c949 ("powerpc: Always restore FPU/VEC/VSX if hardware transactional memory in use")
>>
>>
>> And I guess I need to start running checkkconfigsymbols.py on every
>> commit.
>
> Happy to find a new user :-) You can also run the script on a range
> of commits via '--diff commitA..commitB', which can safe some time.
Yeah I just discovered that, very useful.
But my instinct was to do:
$ ./scripts/checkkconfigsymbols.py --diff HEAD^^^..HEAD
Which didn't work, the regexp is a bit tight, fixed by:
diff --git a/scripts/checkkconfigsymbols.py b/scripts/checkkconfigsymbols.py
index a32e4da4c117..3820f00b066a 100755
--- a/scripts/checkkconfigsymbols.py
+++ b/scripts/checkkconfigsymbols.py
@@ -88,7 +88,7 @@ def parse_options():
if args.commit and args.diff:
sys.exit("Please specify only one option at once.")
- if args.diff and not re.match(r"^[\w\-\.]+\.\.[\w\-\.]+$", args.diff):
+ if args.diff and not re.match(r"^[\w\-\.\^]+\.\.[\w\-\.\^]+$", args.diff):
sys.exit("Please specify valid input in the following format: "
"\'commit1..commit2\'")
cheers
next prev parent reply other threads:[~2016-10-26 10:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 5:57 Valentin Rothberg
2016-10-05 22:54 ` Cyril Bur
[not found] ` <878ttby7vh.fsf@concordia.ellerman.id.au>
2016-10-26 6:25 ` Valentin Rothberg
2016-10-26 10:40 ` Michael Ellerman [this message]
2016-10-26 10:43 ` Valentin Rothberg
2016-10-27 0:11 ` Michael Ellerman
2016-10-27 1:08 ` Cyril Bur
2016-10-27 11:41 ` Michael Ellerman
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=87y41bwfyy.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=cyrilbur@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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
all inboxes | Powered by JetHome®