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 2/3] staging: wlags49_h2: wl_if.h: fixes several coding style issues
Date: Mon, 19 Nov 2012 10:17:33 +0300 [thread overview]
Message-ID: <20121119071732.GD6135@mwanda> (raw)
In-Reply-To: <1353084883-8860-1-git-send-email-johanmeiring@gmail.com>
On Fri, Nov 16, 2012 at 06:54:43PM +0200, Johan Meiring wrote:
> This commit sorts out several coding style issues, including the use of C99 // comments, spaces at the start of lines, spaces before tabs, incorrect brace placement, and macros with complex values that have not been wrapped in parentheses. The only remaining issue is the use of typedefs in two instances, but that's something that the original author might need to have a look at.
>
Could you line wrap your commit message at something like 72-73
characters? I think that's they rule on email, but I forget.
Normally we ask that people break these kinds of changes into
multiple patches.
[patch 1/x] Staging: wlags49_h2: wl_if.h: use tab indents
[patch 2/x] Staging: wlags49_h2: wl_if.h: fix comment style
etc...
> +/*
> +#define HCF_MIN_COMM_QUALITY 0
> +#define HCF_MAX_COMM_QUALITY 92
> +#define HCF_MIN_SIGNAL_LEVEL 47
> +#define HCF_MAX_SIGNAL_LEVEL 138
> +#define HCF_MIN_NOISE_LEVEL 47
> +#define HCF_MAX_NOISE_LEVEL 138
> +#define HCF_0DBM_OFFSET 149
> +*/
Just delete this dead code.
> +#define SIOCSIWNETNAME (SIOCDEVPRIVATE+1)
> +#define SIOCGIWNETNAME (SIOCDEVPRIVATE+2)
> +#define SIOCSIWSTANAME (SIOCDEVPRIVATE+3)
> +#define SIOCGIWSTANAME (SIOCDEVPRIVATE+4)
> +#define SIOCSIWPORTTYPE (SIOCDEVPRIVATE+5)
> +#define SIOCGIWPORTTYPE (SIOCDEVPRIVATE+6)
Could you put spaces around the '+' operator?
#define SIOCSIWNETNAME (SIOCDEVPRIVATE + 1)
regards,
dan carpenter
next prev parent reply other threads:[~2012-11-19 7:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 16:54 [PATCH 2/3] staging: wlags49_h2: wl_if.h: fixes several coding style issues Johan Meiring
2012-11-19 7:17 ` Dan Carpenter [this message]
2012-11-20 13:00 ` Johan Meiring
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=20121119071732.GD6135@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;
as well as URLs for NNTP newsgroup(s).