From: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
To: Kevin Hao <haokexin@gmail.com>, linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Vipin Sharma <vipinsh@google.com>
Subject: Re: [PATCH v2] scripts/tags.sh: Fix the Kconfig tags generation when using latest ctags
Date: Fri, 30 Dec 2022 11:21:24 +0200 [thread overview]
Message-ID: <920366ed-c719-a68d-2857-8c672db5caef@collabora.com> (raw)
In-Reply-To: <20221230025632.1053726-1-haokexin@gmail.com>
On 12/30/22 04:56, Kevin Hao wrote:
> The Kconfig language has already been built-in in the latest ctags, so
> it would error exit if we try to define it as an user-defined language
> via '--langdef=kconfig'. This results that there is no Kconfig tags in
> the final tag file. Fix this by skipping the user Kconfig definition for
> the latest ctags.
>
> Signed-off-by: Kevin Hao <haokexin@gmail.com>
> ---
> v2: Convert 'KCONFIG_ARGS' into array as suggested by Cristian.
>
> scripts/tags.sh | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/scripts/tags.sh b/scripts/tags.sh
> index e137cf15aae9..84775f08260f 100755
> --- a/scripts/tags.sh
> +++ b/scripts/tags.sh
> @@ -264,10 +264,12 @@ exuberant()
> --$CTAGS_EXTRA=+fq --c-kinds=+px --fields=+iaS --langmap=c:+.h \
> "${regex[@]}"
>
> - setup_regex exuberant kconfig
> - all_kconfigs | xargs $1 -a \
> - --langdef=kconfig --language-force=kconfig "${regex[@]}"
> -
> + KCONFIG_ARGS=()
> + if ! $1 --list-languages | grep -iq kconfig; then
> + setup_regex exuberant kconfig
> + KCONFIG_ARGS=(--langdef=kconfig --language-force=kconfig "${regex[@]}")
> + fi
> + all_kconfigs | xargs $1 -a "${KCONFIG_ARGS[@]}"
> }
>
> emacs()
Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
Thanks,
Cristian
prev parent reply other threads:[~2022-12-30 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 2:56 Kevin Hao
2022-12-30 9:21 ` Cristian Ciocaltea [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=920366ed-c719-a68d-2857-8c672db5caef@collabora.com \
--to=cristian.ciocaltea@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=haokexin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vipinsh@google.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®