mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: Joe Perches <joe@perches.com>, Andy Whitcroft <apw@canonical.com>
Cc: linux-kernel@vger.kernel.org, u-boot@lists.denx.de
Subject: Re: [BUG] checkpatch: false positive storage class location
Date: Tue, 4 Jul 2017 23:08:23 +0200	[thread overview]
Message-ID: <fe35e8a3-f2bd-5796-07a9-bdc3b6cee5d1@gmx.de> (raw)
In-Reply-To: <1499201063.19466.2.camel@perches.com>

On 07/04/2017 10:44 PM, Joe Perches wrote:
> On Tue, 2017-07-04 at 21:29 +0200, Heinrich Schuchardt wrote:
>> The U-Boot project uses the same scripts/checkpatch.pl as the Linux
>> kernel. I ran upon the problem below when working on U-Boot. But I
>> guess it should be fixed in the Linux upstream.
>>
>> Running checkpatch for this email produces
>> WARNING: storage class should be at the beginning of the declaration
>>
>> This relates to the parameter with asmlinkage.
>>
>> asmlinkage is at the start of the parameter so I think this a false
>> positive.
>>
>> Signed-off-by: Heinrich.Schuchardt <xypron.glpk@gmx.de>
>> ---
>>
>>  cmd/bootefi.c | 22 +++++++++++++++++-----
>>  1 file changed, 17 insertions(+), 5 deletions(-)
>>
>> diff --git a/cmd/bootefi.c b/cmd/bootefi.c
>> index 771300ee94..4df468307c 100644
>> --- a/cmd/bootefi.c
>> +++ b/cmd/bootefi.c
>> @@ -147,6 +147,12 @@ static void *copy_fdt(void *fdt)
>>  	return new_fdt;
>>  }
>>  
>> +static ulong efi_do_enter(void *image_handle,
>> +		struct efi_system_table *st, asmlinkage ulong (*entry)(
>> +		void *image_handle, struct efi_system_table *st))
>> +{
>> +	return 0;
>> +}
>> +
>>  /*
>>  end
>>  */
> 
> Perhaps this?
> -------------------------
> 
> Allow storage class after comma for function pointers.
> 
> Miscellanea:
> 
> o Add missing semicolon after WARN statement
> ---
>  scripts/checkpatch.pl | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 43171ed88115..c7490ab48ce1 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -5577,9 +5577,10 @@ sub process {
>  		}
>  
>  # Check that the storage class is at the beginning of a declaration
> -		if ($line =~ /\b$Storage\b/ && $line !~ /^.\s*$Storage\b/) {
> +		if ($line =~ /\b$Storage\b/ &&
> +		    $line !~ /^.\s*(?:.*,\s*)?$Storage\b/) {
>  			WARN("STORAGE_CLASS",
> -			     "storage class should be at the beginning of the declaration\n" . $herecurr)
> +			     "storage class should be at the beginning of the declaration\n" . $herecurr);
>  		}
>  
>  # check the location of the inline attribute, that it is between
> 

Thank you. This works for all cases but

+static ulong efi_do_enter(ulong asmlinkage (*entry)(void *image_handle,
+                          struct efi_system_table *st))
+{
+       return 0;
+}
+

Here I get
WARNING: space prohibited between function name and open parenthesis '('
where I would have expected
WARNING: storage class should be at the beginning of the declaration

Best regards

Heinrich Schuchardt

  reply	other threads:[~2017-07-04 21:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-04 19:29 Heinrich Schuchardt
2017-07-04 20:44 ` Joe Perches
2017-07-04 21:08   ` Heinrich Schuchardt [this message]
2017-07-05 12:01     ` Joe Perches

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=fe35e8a3-f2bd-5796-07a9-bdc3b6cee5d1@gmx.de \
    --to=xypron.glpk@gmx.de \
    --cc=apw@canonical.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=u-boot@lists.denx.de \
    /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®