From: Andy Whitcroft <apw@shadowen.org>
To: Timur Tabi <timur@freescale.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkpatch: add __asm__ to function-space-paren exception list
Date: Mon, 4 Feb 2008 11:22:03 +0000 [thread overview]
Message-ID: <20080204112203.GA19879@shadowen.org> (raw)
In-Reply-To: <12016486482483-git-send-email-timur@freescale.com>
On Tue, Jan 29, 2008 at 05:17:28PM -0600, Timur Tabi wrote:
> checkpatch.pl thinks that __asm__ is a function name, so it complains about
> a space between the function name and a parenthesis when it sees
> "__asm__ ("mov ax,bx")".
>
> This change will also encourage developers to use '__asm__' instead of 'asm'.
>
> Signed-off-by: Timur Tabi <timur@freescale.com>
> ---
> scripts/checkpatch.pl | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 579f50f..971c822 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -1115,7 +1115,7 @@ sub process {
>
> # check for spaces between functions and their parentheses.
> while ($line =~ /($Ident)\s+\(/g) {
> - if ($1 !~ /^(?:if|for|while|switch|return|volatile|__volatile__|__attribute__|format|__extension__|Copyright|case)$/ &&
> + if ($1 !~ /^(?:if|for|while|switch|return|volatile|__volatile__|__attribute__|format|__extension__|Copyright|case|__asm__)$/ &&
> $line !~ /$Type\s+\(/ && $line !~ /^.\#\s*define\b/) {
> WARN("no space between function name and open parenthesis '('\n" . $herecurr);
> }
> --
It truly is not clear what "type" of thing an __asm__ is these days.
Cirtainly it seems we can use it as an attribute of a type:
register unsigned long __r16 __asm__("$16") = rtc_access->function;
and yet also in its more traditional form:
__asm__(" call foo");
The latter form feels like a function? But cirtainly in the examples it
is shown with a space some of the time, and not others. Is __asm__ an
attribute of the null function (;) in this context or ... well ?
This patch really just removes any checks for spacing on __asm__ do we
have a preferred style for these? Attributes do seem to have spaces,
though in their most attribute like usage the __asm__ "attribute" does
not seem to be used with a space, so far anyhow.
Oh and why are we preferring the use of __asm__ over asm? They both
seem valid. Should we be recommending one over the other?
-apw
next prev parent reply other threads:[~2008-02-04 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 23:17 [PATCH] checkpatch: add __asm__ to function-space-paren exception list Timur Tabi
2008-02-04 11:22 ` Andy Whitcroft [this message]
2008-02-04 16:38 ` Timur Tabi
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=20080204112203.GA19879@shadowen.org \
--to=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=timur@freescale.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