From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 0/3] Add script to detect collisions in commandchars
Date: Sat, 26 Jan 2019 08:15:56 -0800 [thread overview]
Message-ID: <20190126161556.GH4240@linux.ibm.com> (raw)
In-Reply-To: <85136a6e-539f-4c51-0c49-fce3500e957d@gmail.com>
On Sun, Jan 27, 2019 at 12:07:32AM +0900, Akira Yokosawa wrote:
> Hi Paul,
>
> I mentioned in an earlier patch submission that to add collision
> check of commandchars in fcvextract.pl was on my to-do list.
>
> It turned out that fcvextract.pl is already complicated and
> I changed my mind to add a separate script to check .fcv files for
> the collisions.
>
> Patch #1 adds the script as utilities/checkfcv.pl.
> Patch #2 adds the invocations of the script in Makefile. It also
> suppresses the echo of commands in the recipes.
> Patch #3 fixes a couple of collisions detected by the script.
>
> The two collisions were made by myself. This automatic check
> looks promising to me.
Looks promising, let's see how it goes -- queued and pushed, thank you!
Thanx, Paul
> Thanks, Akira
> --
> Akira Yokosawa (3):
> Add checkfcv.pl
> Makefile: Invoke checkfcv.pl in -> .fcv recipes
> CodeSamples: Fix commandchars collision
>
> CodeSamples/defer/route_hazptr.c | 2 +-
> .../formal/litmus/C-ISA2+o-r+a-r+a-r+a-o.litmus | 2 +-
> Makefile | 8 ++-
> utilities/checkfcv.pl | 78 ++++++++++++++++++++++
> 4 files changed, 85 insertions(+), 5 deletions(-)
> create mode 100755 utilities/checkfcv.pl
>
> --
> 2.7.4
>
prev parent reply other threads:[~2019-01-26 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 15:07 [PATCH 0/3] Add script to detect collisions in commandchars Akira Yokosawa
2019-01-26 15:10 ` [PATCH 1/3] Add checkfcv.pl Akira Yokosawa
2019-01-26 15:11 ` [PATCH 2/3] Makefile: Invoke checkfcv.pl in -> .fcv recipes Akira Yokosawa
2019-01-26 15:12 ` [PATCH 3/3] CodeSamples: Fix commandchars collision Akira Yokosawa
2019-01-26 16:15 ` Paul E. McKenney [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=20190126161556.GH4240@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=akiyks@gmail.com \
--cc=perfbook@vger.kernel.org \
/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