Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756160AbbLGQx5 (ORCPT ); Mon, 7 Dec 2015 11:53:57 -0500 Received: from mx2.suse.de ([195.135.220.15]:39105 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755648AbbLGQxz (ORCPT ); Mon, 7 Dec 2015 11:53:55 -0500 Subject: Re: [PATCH v2 8/8] treewide: Remove newlines inside DEFINE_PER_CPU() macros To: David Laight , "linux-kbuild@vger.kernel.org" References: <1449242787-16598-1-git-send-email-mmarek@suse.com> <1449242787-16598-9-git-send-email-mmarek@suse.com> <063D6719AE5E284EB5DD2968C1650D6D1CBE695F@AcuExch.aculab.com> Cc: "linux-kernel@vger.kernel.org" , "linux-ia64@vger.kernel.org" , "xen-devel@lists.xenproject.org" , "linux-acpi@vger.kernel.org" , "rds-devel@oss.oracle.com" , "netdev@vger.kernel.org" From: Michal Marek Message-ID: <5665B9A0.5060009@suse.com> Date: Mon, 7 Dec 2015 17:53:52 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D1CBE695F@AcuExch.aculab.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 788 Lines: 21 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/