From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Mario J. Rugiero" <mrugiero@gmail.com>
Cc: devel@driverdev.osuosl.org, chris.park@atmel.com,
austin.shin@atmel.com, gregkh@linuxfoundation.org,
linux-wireless@vger.kernel.org, johnny.kim@atmel.com,
tony.cho@atmel.com, leo.kim@atmel.com
Subject: Re: [PATCH 1/1] staging: cleanup: Fix incompatible type comparison in wilc1000/host_interface.c
Date: Wed, 2 Dec 2015 16:29:23 +0300 [thread overview]
Message-ID: <20151202132923.GV18797@mwanda> (raw)
In-Reply-To: <1448928544-3534-1-git-send-email-mrugiero@gmail.com>
Put v2 in the subject. Also the subsystem prefix is:
[PATCH v3] staging: wilc1000: ...
On Mon, Nov 30, 2015 at 09:09:04PM -0300, Mario J. Rugiero wrote:
> This patch replaces an "if (ptr > 0)" comparison that seems to be a
> confusing way to check for null by a simpler "if (ptr)" check.
>
> Signed-off-by: Mario J. Rugiero <mrugiero@gmail.com>
> ---
v2: Remove the != NULL because checkpatch complains.
> drivers/staging/wilc1000/host_interface.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/wilc1000/host_interface.c b/drivers/staging/wilc1000/host_interface.c
> index d5b7725..0c87f6c 100644
> --- a/drivers/staging/wilc1000/host_interface.c
> +++ b/drivers/staging/wilc1000/host_interface.c
> @@ -2270,7 +2270,7 @@ static void Handle_AddBeacon(struct host_if_drv *hif_drv,
> *pu8CurrByte++ = ((pstrSetBeaconParam->tail_len >> 16) & 0xFF);
> *pu8CurrByte++ = ((pstrSetBeaconParam->tail_len >> 24) & 0xFF);
>
> - if (pstrSetBeaconParam->tail > 0)
> + if (pstrSetBeaconParam->tail)
Probably the intention was to check if "pstrSetBeaconParam->tail_len > 0"
but I'm not sure. The wilc1000 maintainers are very responsive though
so maybe they will know for sure.
regards,
dan carpenter
next prev parent reply other threads:[~2015-12-02 13:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 0:09 [PATCH 1/1] staging: cleanup: Fix incompatible type comparison in wilc1000/host_interface.c Mario J. Rugiero
2015-12-02 13:29 ` Dan Carpenter [this message]
2015-12-02 15:12 ` Mario J. Rugiero
2015-12-03 8:24 ` glen lee
2015-12-03 15:13 ` Mario J. Rugiero
2015-12-03 15:17 ` Dan Carpenter
2015-12-03 15:18 ` Mario J. Rugiero
2015-12-03 15:21 ` Dan Carpenter
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=20151202132923.GV18797@mwanda \
--to=dan.carpenter@oracle.com \
--cc=austin.shin@atmel.com \
--cc=chris.park@atmel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=johnny.kim@atmel.com \
--cc=leo.kim@atmel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mrugiero@gmail.com \
--cc=tony.cho@atmel.com \
/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