From: Dan Carpenter <error27@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] drivers: rename some function parameters from 'register'
Date: Wed, 14 Sep 2011 21:25:17 +0000 [thread overview]
Message-ID: <20110914212517.GF3789@shale.localdomain> (raw)
In-Reply-To: <1315832341-917-1-git-send-email-cpeterso@cpeterso.com>
On Mon, Sep 12, 2011 at 08:59:01AM -0400, Chris Peterson wrote:
> Some function prototypes declare an 'int register' parameter. gcc -W warns
> "‘register’ is not at beginning of declaration" because the compiler thinks
> the parameter has been marked as a 'register' variable but the author
> just wanted to name the parameter "register" (which is a reserved keyword).
>
> Signed-off-by: Chris Peterson <cpeterso@cpeterso.com>
This needs to be broken up into separate patches by file. The
problem is that you have four maintainers and they each can only
take the chunk that affects their subsystem.
> --- a/drivers/isdn/hardware/eicon/platform.h
> +++ b/drivers/isdn/hardware/eicon/platform.h
> @@ -206,7 +206,7 @@ void PCIread (byte bus, byte func, int offset, void* data, int length, void* pci
> /*
> ** I/O Port utilities
> */
> -int diva_os_register_io_port (void *adapter, int register, unsigned long port,
> +int diva_os_register_io_port (void *adapter, int reg, unsigned long port,
> unsigned long length, const char* name, int id);
Instead of using "reg" for this one, it probably would be better to
use "on". That's how it's named in the .c file.
regards,
dan carpenter
next prev parent reply other threads:[~2011-09-14 21:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 12:59 [PATCH] drivers: rename some function parameters from 'register' to 'reg' Chris Peterson
2011-09-14 21:25 ` Dan Carpenter [this message]
2011-09-15 6:38 ` [PATCH] drivers: rename some function parameters from 'register' Chris Peterson
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=20110914212517.GF3789@shale.localdomain \
--to=error27@gmail.com \
--cc=kernel-janitors@vger.kernel.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