public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: glen lee <glen.lee@atmel.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: <kbuild-all@01.org>, <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: drivers/staging/wilc1000/host_interface.c:4135:5: error: conflicting types for 'host_int_init'
Date: Mon, 16 Nov 2015 11:04:39 +0900	[thread overview]
Message-ID: <564939B7.8050204@atmel.com> (raw)
In-Reply-To: <201511150731.YalOWe68%fengguang.wu@intel.com>

Hi fengguang,

This was fixed on staging-testing branch but not yet merged.

8224ec3e05b626b1b18ed0c107f2a2b1da979553 fixes this error also.

regards,
glen lee.


On 2015년 11월 15일 08:15, kbuild test robot wrote:
> Hi Glen,
>
> FYI, the error/warning still remains.
>
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   12b76f3bf336388916ddf8047156f9e9993ff4e9
> commit: d5382219138db78b82631501b0f614e5fd012ad1 staging: wilc1000: host_int_init: add argument net_device
> date:   2 weeks ago
> config: i386-allyesconfig (attached as .config)
> reproduce:
>          git checkout d5382219138db78b82631501b0f614e5fd012ad1
>          # save the attached .config to linux build tree
>          make ARCH=i386
>
> All errors (new ones prefixed by >>):
>
>     In file included from drivers/staging/wilc1000/host_interface.c:5:0:
>     drivers/staging/wilc1000/host_interface.h:914:50: warning: 'struct net_device' declared inside parameter list
>      s32 host_int_init(struct net_device *dev, struct host_if_drv **phWFIDrv);
>                                                       ^
>     drivers/staging/wilc1000/host_interface.h:914:50: warning: its scope is only this definition or declaration, which is probably not what you want
>>> drivers/staging/wilc1000/host_interface.c:4135:5: error: conflicting types for 'host_int_init'
>      s32 host_int_init(struct net_device *dev, struct host_if_drv **hif_drv_handler)
>          ^
>     In file included from drivers/staging/wilc1000/host_interface.c:5:0:
>     drivers/staging/wilc1000/host_interface.h:914:5: note: previous declaration of 'host_int_init' was here
>      s32 host_int_init(struct net_device *dev, struct host_if_drv **phWFIDrv);
>          ^
>
> vim +/host_int_init +4135 drivers/staging/wilc1000/host_interface.c
>
>    4129	
>    4130	void host_int_send_network_info_to_host
>    4131		(u8 *macStartAddress, u16 u16RxFrameLen, s8 s8Rssi)
>    4132	{
>    4133	}
>    4134	
>> 4135	s32 host_int_init(struct net_device *dev, struct host_if_drv **hif_drv_handler)
>    4136	{
>    4137		s32 result = 0;
>    4138		struct host_if_drv *hif_drv;
>
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation


      reply	other threads:[~2015-11-16  2:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-14 23:15 drivers/staging/wilc1000/host_interface.c:4135:5: error: conflicting types for 'host_int_init' kbuild test robot
2015-11-16  2:04 ` glen lee [this message]

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=564939B7.8050204@atmel.com \
    --to=glen.lee@atmel.com \
    --cc=fengguang.wu@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    /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