From: Johnny Kim <johnny.kim@atmel.com>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Chris Park <chris.park@atmel.com>,
"Rachel Kim" <rachel.kim@atmel.com>, <tony.cho@atmel.com>,
<Nicolas.FERRE@atmel.com>, Dean Lee <dean.lee@atmel.com>,
<austin.shin@atmel.com>
Subject: Re: [PATCH 2/3] staging: wilc1000: wilc_wlan_cfg_get(): replace integer with void pointer
Date: Fri, 10 Jul 2015 17:11:11 +0900 [thread overview]
Message-ID: <559F7E1F.7070407@atmel.com> (raw)
In-Reply-To: <CAGRGNgVwVKq2JQ5FypdAZvLUoYPEL+MQ=yPsMJo3onOfWin7vQ@mail.gmail.com>
On 2015년 07월 10일 15:25, Julian Calaby wrote:
> Hi Johnny,
>
> On Fri, Jul 10, 2015 at 3:55 PM, Johnny Kim <johnny.kim@atmel.com> wrote:
>> Last argument of wilc_wlan_cfg_get function is actually structure's address.
>> This should be changed to be compatible with 64bit machine.
>> Because wilc_wlan_cfg_get function is mapped by function pointer later,
>> wilc_wlan_oup_t.wlan_cfg_get should be changed together.
>>
>> tstrWILC_WFIDrv structure is defined after wilc_wlan_oup_t.wlan_cfg_get
>> is defined. So, this patch changes the argument to void type pointer.
> Why not add a patch moving the structure definition before
> wilc_wlan_oup_t.wlan_cfg_get is defined?
Current patch focus on accessing 64bit address rightly.
The define order you and I mentioned should be repaired with another subject
because of complexity among files.
>> Signed-off-by: Johnny Kim <johnny.kim@atmel.com>
>> ---
>> drivers/staging/wilc1000/coreconfigurator.c | 2 +-
>> drivers/staging/wilc1000/wilc_wlan.c | 2 +-
>> drivers/staging/wilc1000/wilc_wlan_if.h | 2 +-
>> 3 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/staging/wilc1000/coreconfigurator.c b/drivers/staging/wilc1000/coreconfigurator.c
>> index b069614..141d7b4 100644
>> --- a/drivers/staging/wilc1000/coreconfigurator.c
>> +++ b/drivers/staging/wilc1000/coreconfigurator.c
>> @@ -2094,7 +2094,7 @@ s32 SendConfigPkt(u8 u8Mode, tstrWID *pstrWIDs,
>> (counter == u32WIDsCount - 1));
>> if (!gpstrWlanOps->wlan_cfg_get(!counter,
>> pstrWIDs[counter].u16WIDid,
>> - (counter == u32WIDsCount - 1), drvHandler)) {
>> + (counter == u32WIDsCount - 1), (void *)drvHandler)) {
> If I recall correctly, you shouldn't need void * casts.
>
> Thanks,
>
Thanks.
Johnny.
next prev parent reply other threads:[~2015-07-10 8:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 5:55 [PATCH 0/3] staging: wilc1000: rework integer value for x64 Johnny Kim
2015-07-10 5:55 ` [PATCH 1/3] staging: wilc1000: wilc_wlan_cfg_commit(): replace integer with pointer Johnny Kim
2015-07-10 6:20 ` Julian Calaby
2015-07-10 7:58 ` Johnny Kim
2015-07-10 10:05 ` Julian Calaby
2015-07-10 5:55 ` [PATCH 2/3] staging: wilc1000: wilc_wlan_cfg_get(): replace integer with void pointer Johnny Kim
2015-07-10 6:25 ` Julian Calaby
2015-07-10 8:11 ` Johnny Kim [this message]
2015-07-10 10:17 ` Julian Calaby
2015-07-14 21:12 ` Greg KH
2015-07-10 5:55 ` [PATCH 3/3] staging: wilc1000: wilc_wlan_cfg_set(): " Johnny Kim
2015-07-10 6:26 ` Julian Calaby
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=559F7E1F.7070407@atmel.com \
--to=johnny.kim@atmel.com \
--cc=Nicolas.FERRE@atmel.com \
--cc=austin.shin@atmel.com \
--cc=chris.park@atmel.com \
--cc=dean.lee@atmel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=julian.calaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rachel.kim@atmel.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).