From: Michal Marek <mmarek@suse.com>
To: David Laight <David.Laight@ACULAB.COM>,
"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"rds-devel@oss.oracle.com" <rds-devel@oss.oracle.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH v2 8/8] treewide: Remove newlines inside DEFINE_PER_CPU() macros
Date: Mon, 7 Dec 2015 17:53:52 +0100 [thread overview]
Message-ID: <5665B9A0.5060009@suse.com> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D1CBE695F@AcuExch.aculab.com>
On 2015-12-07 17:33, David Laight wrote:
> From: Michal Marek
>> Sent: 04 December 2015 15:26
>> Otherwise make tags can't parse them:
>>
>> ctags: Warning: arch/ia64/kernel/smp.c:60: null expansion of name pattern "\1"
> ...
>
> Seems to me you need to fix ctags.
I'm sure the maintainers of ctags and etags would accept patches to
describe a custom context-free grammar via commandline options, but
until then, let's continue using the regular expressions in tags.sh and
remove newlines in macros that tags.sh is trying to expand.
Michal
next prev parent reply other threads:[~2015-12-07 16:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 15:26 [PATCH v2 0/8] scripts/tags.sh cleanup Michal Marek
2015-12-04 15:26 ` [PATCH v2 1/8] tags: Treat header files as C code Michal Marek
2015-12-04 15:26 ` [PATCH v2 2/8] aic7xxx: Avoid name collision with <linux/list.h> Michal Marek
2015-12-04 15:26 ` [PATCH v2 3/8] tags: Fix erroneous pattern match in a comment Michal Marek
2015-12-04 15:26 ` [PATCH v2 4/8] tags: Process Kconfig files in a single pass Michal Marek
2015-12-04 15:26 ` [PATCH v2 5/8] tags: Do not try to index defconfigs Michal Marek
2015-12-04 15:26 ` [PATCH v2 6/8] tags: Drop the _PE rule Michal Marek
2015-12-04 15:26 ` [PATCH v2 7/8] tags: Unify emacs and exuberant rules Michal Marek
2016-01-05 21:51 ` Michal Marek
2015-12-04 15:26 ` [PATCH v2 8/8] treewide: Remove newlines inside DEFINE_PER_CPU() macros Michal Marek
2015-12-07 16:33 ` David Laight
2015-12-07 16:53 ` Michal Marek [this message]
2015-12-07 17:04 ` Joe Perches
2015-12-07 17:19 ` Michal Marek
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=5665B9A0.5060009@suse.com \
--to=mmarek@suse.com \
--cc=David.Laight@ACULAB.COM \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).