linux-kernel - Re: [PATCH] staging - pohmelfs: Storage class should be before const qualifier

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 26 Apr 2009 22:01:35 +0400
From:	Evgeniy Polyakov <zbr@...emap.net>
To:	Tobias Klauser <tklauser@...tanz.ch>
Cc:	gregkh@...e.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging - pohmelfs: Storage class should be before const qualifier

On Sun, Apr 26, 2009 at 03:06:09PM +0200, Tobias Klauser (tklauser@...tanz.ch) wrote:
> The C99 specification states in section 6.11.5:
> 
> The placement of a storage-class specifier other than at the beginning
> of the declaration specifiers in a declaration is an obsolescent
> feature.
> 
> Signed-off-by: Tobias Klauser <tklauser@...tanz.ch>

Looks good, thank you.
Greg, please put it into the queue.

> ---
>  drivers/staging/pohmelfs/inode.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/staging/pohmelfs/inode.c b/drivers/staging/pohmelfs/inode.c
> index b2eaf90..779445e 100644
> --- a/drivers/staging/pohmelfs/inode.c
> +++ b/drivers/staging/pohmelfs/inode.c
> @@ -943,7 +943,7 @@ err_out_unlock:
>  	return ret;
>  }
>  
> -const static struct file_operations pohmelfs_file_ops = {
> +static const struct file_operations pohmelfs_file_ops = {
>  	.open		= generic_file_open,
>  	.fsync		= pohmelfs_fsync,
>  
> -- 
> 1.6.2.4

-- 
	Evgeniy Polyakov
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/