From: glen lee <glen.lee@atmel.com>
To: "Mario J. Rugiero" <mrugiero@gmail.com>,
Dan Carpenter <dan.carpenter@oracle.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: Thu, 3 Dec 2015 17:24:16 +0900 [thread overview]
Message-ID: <565FFC30.10801@atmel.com> (raw)
In-Reply-To: <565F0A79.90100@gmail.com>
On 2015년 12월 03일 00:12, Mario J. Rugiero wrote:
> OK. Since the maintainers are CC'd, I guess I should wait for a
> clarification about this?
Hi Mario,
The purpose of that is to check if tail is null or not. if it is not null, there is tail
to send, so copy to buff.
regards,
glen lee.
>
> El 02/12/15 a las 10:29, Dan Carpenter escribió:
>> 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
>>
>>
>
> _______________________________________________
> devel mailing list
> devel@linuxdriverproject.org
> http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2015-12-03 8:20 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
2015-12-02 15:12 ` Mario J. Rugiero
2015-12-03 8:24 ` glen lee [this message]
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=565FFC30.10801@atmel.com \
--to=glen.lee@atmel.com \
--cc=austin.shin@atmel.com \
--cc=chris.park@atmel.com \
--cc=dan.carpenter@oracle.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;
as well as URLs for NNTP newsgroup(s).