All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Tony Cho <tony.cho@atmel.com>,
	devel@driverdev.osuosl.org, rachel.kim@atmel.com,
	chris.park@atmel.com, linux-wireless@vger.kernel.org,
	johnny.kim@atmel.com, jude.lee@atmel.com, leo.kim@atmel.com
Subject: Re: [PATCH 2/5] staging: wilc1000: change void pointer type to real type
Date: Fri, 14 Aug 2015 19:01:49 -0700	[thread overview]
Message-ID: <20150815020149.GA14400@kroah.com> (raw)
In-Reply-To: <20150814062613.GB421@sudip-pc>

On Fri, Aug 14, 2015 at 11:56:13AM +0530, Sudip Mukherjee wrote:
> On Thu, Aug 13, 2015 at 01:41:20PM +0900, Tony Cho wrote:
> > From: Johnny Kim <johnny.kim@atmel.com>
> > 
> > This patch changes the void pointer member of the tstrHostIFmsg to the
> > real data type because the void pointer type is ambiguous and not
> > readable.
> > 
> > Signed-off-by: Johnny Kim <johnny.kim@atmel.com>
> > Signed-off-by: Tony Cho <tony.cho@atmel.com>
> > ---
> This patch is introducing some new warnings like:
> 
> drivers/staging/wilc1000/host_interface.c: In function ‘host_int_set_wfi_drv_handler’:
> drivers/staging/wilc1000/host_interface.c:5817:66: warning: assignment
> makes integer from pointer without a cast [enabled by default]
>   strHostIFmsg.uniHostIFmsgBody.strHostIfSetDrvHandler.u32Address = u32address;

That warning doesn't seem to have anything to do with this patch, odd...

  reply	other threads:[~2015-08-15  2:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-13  4:41 [PATCH 0/5] staging: wilc1000: 64bit build patch Tony Cho
2015-08-13  4:41 ` [PATCH 1/5] staging: wilc1000: replace WILC_WFIDrvHandle by tstrWILC_WFIDrv Tony Cho
2015-08-13  4:41 ` [PATCH 2/5] staging: wilc1000: change void pointer type to real type Tony Cho
2015-08-14  6:26   ` Sudip Mukherjee
2015-08-15  2:01     ` Greg KH [this message]
2015-08-13  4:41 ` [PATCH 3/5] staging: wilc1000: clarify the argument type Tony Cho
2015-08-13  4:41 ` [PATCH 4/5] staging: wilc1000: use the real data type Tony Cho
2015-08-15  2:04   ` Greg KH
2015-08-13  4:41 ` [PATCH 5/5] staging: wilc1000: use id value as argument Tony Cho
2015-08-13 14:49   ` Dan Carpenter
2015-08-18  3:10     ` Johnny Kim
2015-08-18  9:12       ` Dan Carpenter
2015-08-19  7:58         ` Johnny Kim
2015-08-19 10:05           ` Dan Carpenter
  -- strict thread matches above, loose matches on Subject: below --
2015-08-10  5:58 [PATCH 0/5] 64 bit build patch Tony Cho
2015-08-10  5:58 ` [PATCH 2/5] staging: wilc1000: change void pointer type to real type Tony Cho

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=20150815020149.GA14400@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chris.park@atmel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=johnny.kim@atmel.com \
    --cc=jude.lee@atmel.com \
    --cc=leo.kim@atmel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rachel.kim@atmel.com \
    --cc=sudipm.mukherjee@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.