All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: perfbook@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH -perfbook 3/3] cleverefcheck.pl: Add patterns to catch QQz positioning issues
Date: Thu, 10 Feb 2022 00:17:24 +0900	[thread overview]
Message-ID: <3224bc4a-39f0-184d-dd89-aca998a2383d@gmail.com> (raw)
In-Reply-To: <3754e966-dcae-bc66-1dfe-cc5dc4718bed@gmail.com>

On Thu, 10 Feb 2022 00:12:23 +0900,
Akira Yokosawa wrote:
> Add patterns in cleverefcheck.pl to catch:
> 
>   - A plain QQz or grouped QQzs at the beginning of a section
>   - Consecutive QQzs not properly grouped
> 
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>

Paul,

You can see how the added pattern works by applying only 3/3
on current master e4815ca92805 ("memorder: Fix typos"), and
run "make punctcheck".

It will complain QQzs Patches 1/3 and 2/3 fix.

        Thanks, Akira

> ---
>  utilities/cleverefcheck.pl | 18 ++++++++++++++++++
>  1 file changed, 18 insertions(+)
> 
> diff --git a/utilities/cleverefcheck.pl b/utilities/cleverefcheck.pl
> index 6e9a59e8..d92de5ac 100755
> --- a/utilities/cleverefcheck.pl
> +++ b/utilities/cleverefcheck.pl
[...]


  reply	other threads:[~2022-02-09 15:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09 15:06 [PATCH -perfbook 1/3] intro, together: Promote section-opening QQzs to 'essential' Akira Yokosawa
2022-02-09 15:08 ` [PATCH -perfbook 2/3] defer, together: Group consecutive QQzs Akira Yokosawa
2022-02-09 15:12 ` [PATCH -perfbook 3/3] cleverefcheck.pl: Add patterns to catch QQz positioning issues Akira Yokosawa
2022-02-09 15:17   ` Akira Yokosawa [this message]
2022-02-09 21:31 ` [PATCH -perfbook 1/3] intro, together: Promote section-opening QQzs to 'essential' Paul E. McKenney

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=3224bc4a-39f0-184d-dd89-aca998a2383d@gmail.com \
    --to=akiyks@gmail.com \
    --cc=paulmck@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.