From: Dan Carpenter <dan.carpenter@oracle.com>
To: Johan Meiring <johanmeiring@gmail.com>
Cc: pe1dnn@amsat.org, jkosina@suse.cz, standby24x7@gmail.com,
viro@zeniv.linux.org.uk, gregkh@linuxfoundation.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 8/8] staging: wlags49_h2: ap_h2.c: fixes inconsistent spacing around *
Date: Wed, 21 Nov 2012 11:34:18 +0300 [thread overview]
Message-ID: <20121121083417.GD11248@mwanda> (raw)
In-Reply-To: <1353422700-14485-7-git-send-email-johanmeiring@gmail.com>
On Tue, Nov 20, 2012 at 04:45:00PM +0200, Johan Meiring wrote:
> This commit fixes an inconsistent spacing issue around *
>
The others are good, but this one is not right.
> Signed-off-by: Johan Meiring <johanmeiring@gmail.com>
> ---
> drivers/staging/wlags49_h2/ap_h2.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/wlags49_h2/ap_h2.c b/drivers/staging/wlags49_h2/ap_h2.c
> index e524153..c2d43ec 100644
> --- a/drivers/staging/wlags49_h2/ap_h2.c
> +++ b/drivers/staging/wlags49_h2/ap_h2.c
> @@ -3256,7 +3256,7 @@ static const CFG_PROG_STRCT fw_image_code[] = {
> 0x0146, /* sizeof(fw_image_1_data), */
> 0x00000060, /* Target address in NIC Memory */
> 0x0000, /* CRC: yes/no TYPE: primary/station/tertiary */
> - (hcf_8 FAR *) fw_image_1_data
> + (hcf_8 FAR*) fw_image_1_data
We don't use far pointers in linux. When you're casting something
there is no space between the cat operation and the variable. The
reason is that casting is a high precedence operation.
More readable: (char *)p + 1;
Less readable: (char *) p + 1;
In the first line it's obvious that we cast first and then add 1.
So this should be:
(hcf_8 *)fw_image_1_data,
regards,
dan carpenter
prev parent reply other threads:[~2012-11-21 8:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 14:44 [PATCH 2/8] staging: wlags49_h2: wl_if.h: fixes tab indentation Johan Meiring
2012-11-20 14:44 ` [PATCH 3/8] staging: wlags49_h2: wl_if.h: fixes spaces-before-tabs issue Johan Meiring
2012-11-20 14:44 ` [PATCH 4/8] staging: wlags49_h2: wl_if.h: fixes 80 char line length issues Johan Meiring
2012-11-20 14:44 ` [PATCH 5/8] staging: wlags49_h2: wl_if.h: fixes brace placement Johan Meiring
2012-11-20 14:44 ` [PATCH 6/8] staging: wlags49_h2: wl_if.h: gets rid of C99 // comments Johan Meiring
2012-11-20 14:44 ` [PATCH 7/8] staging: wlags49_h2: ap_h2.c: fixes spaces-before-tabs problems Johan Meiring
2012-11-20 14:45 ` [PATCH 8/8] staging: wlags49_h2: ap_h2.c: fixes inconsistent spacing around * Johan Meiring
2012-11-21 8:34 ` Dan Carpenter [this message]
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=20121121083417.GD11248@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=johanmeiring@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pe1dnn@amsat.org \
--cc=standby24x7@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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