From: Marc Zyngier <maz@kernel.org>
To: Zackary Liu <zackary.liu.pro@gmail.com>
Cc: masahiroy@kernel.org, ripxorip@gmail.com,
gregkh@linuxfoundation.org, matthieu.baerts@tessares.net,
mpe@ellerman.id.au, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tags: add a space regex to DECLARE_BITMAP
Date: Tue, 02 Nov 2021 16:08:29 +0000 [thread overview]
Message-ID: <874k8ua6bm.wl-maz@kernel.org> (raw)
In-Reply-To: <CAOk_PdPzKukZZiQJ2HYN_j3Zw_t7UXUqqcjDb4OBB39o-LbvNA@mail.gmail.com>
On Tue, 02 Nov 2021 14:25:19 +0000,
Zackary Liu <zackary.liu.pro@gmail.com> wrote:
>
> Hi Marc,
>
> On Tue, Nov 2, 2021 at 12:53 AM Marc Zyngier <maz@kernel.org> wrote:
> >
> > On 2021-11-01 15:59, Zhaoyu Liu wrote:
> > > When "make tags", it prompts a warning:
> > >
> > > ctags: Warning: drivers/pci/controller/pcie-apple.c:150:
> > > null expansion of name pattern "\1"
> > >
> > > The reason is that there is an indentation beside arguments of
> > > DECLARE_BITMAP, but it can parsed normally by gtags. It's also
> > > allowed in C.
> > >
> > > So fix this regex temporarily, and wait for better solutions
> > > applied to other regexs.
> > >
> > > Reviewed-by: Marc Zyngier <maz@kernel.org>
> >
> > No, please! I never reviewed this patch. I *suggested*i it [1]
> > as a potential avenue for improvement.
> >
> > You cannot put this tag on a patch unless someone explicitly
> > grants it.
> >
>
> I'm really sorry that I used the wrong "Reviewed-by" tag,
> Perhaps "Suggested-by" tag would be more appropriate.
Yes, that'd be the right one.
>
> Sorry again.
>
> > > Signed-off-by: Zhaoyu Liu <zackary.liu.pro@gmail.com>
> > > ---
> > > scripts/tags.sh | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/scripts/tags.sh b/scripts/tags.sh
> > > index b24bfaec6290..7e5f19391f20 100755
> > > --- a/scripts/tags.sh
> > > +++ b/scripts/tags.sh
> > > @@ -186,7 +186,7 @@ regex_c=(
> > >
> > >
> '/\<DEFINE_\(RT_MUTEX\|MUTEX\|SEMAPHORE\|SPINLOCK\)(\([[:alnum:]_]*\)/\2/v/'
> > >
> '/\<DEFINE_\(RAW_SPINLOCK\|RWLOCK\|SEQLOCK\)(\([[:alnum:]_]*\)/\2/v/'
> > > '/\<DECLARE_\(RWSEM\|COMPLETION\)(\([[:alnum:]_]\+\)/\2/v/'
> > > - '/\<DECLARE_BITMAP(\([[:alnum:]_]*\)/\1/v/'
> > > + '/\<DECLARE_BITMAP([[:space:]]*\([[:alnum:]_]*\)/\1/v/'
> > > '/\(^\|\s\)\(\|L\|H\)LIST_HEAD(\([[:alnum:]_]*\)/\3/v/'
> > > '/\(^\|\s\)RADIX_TREE(\([[:alnum:]_]*\)/\2/v/'
> > > '/\<DEFINE_PER_CPU([^,]*, *\([[:alnum:]_]*\)/\1/v/'
> >
> > More importantly, and assuming this is the correct approach,
> > why should we limit this to DECLARE_BITMAP()?
>
> I will try to come up with a better approach, and commit [ patch v2
> ] later.
You could try and apply the same approach consistently for all
macros. Since you are using ctags, you're in a good position to test
it and work out whether this is a sensible approach.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2021-11-02 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 15:59 [PATCH] tags: add a space regex to DECLARE_BITMAP Zhaoyu Liu
2021-11-01 16:53 ` Marc Zyngier
[not found] ` <CAOk_PdPzKukZZiQJ2HYN_j3Zw_t7UXUqqcjDb4OBB39o-LbvNA@mail.gmail.com>
2021-11-02 16:08 ` Marc Zyngier [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=874k8ua6bm.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=matthieu.baerts@tessares.net \
--cc=mpe@ellerman.id.au \
--cc=ripxorip@gmail.com \
--cc=zackary.liu.pro@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