From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: punit vara <punitvara@gmail.com>
Cc: glen lee <glen.lee@atmel.com>,
devel@driverdev.osuosl.org, chris.park@atmel.com,
Austin Shin <austin.shin@atmel.com>,
Greg KH <gregkh@linuxfoundation.org>,
linux-wireless@vger.kernel.org, johnny.kim@atmel.com,
linux-kernel@vger.kernel.org, tony.cho@atmel.com,
leo.kim@atmel.com, Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH V2] Staging: wilc1000: Fix build break due to undeclared *wilc and implicit declaration of init_irq
Date: Mon, 9 Nov 2015 15:53:42 +0530 [thread overview]
Message-ID: <20151109102342.GA3868@sudip-pc> (raw)
In-Reply-To: <CABXAfNKhtdRSm1BJK+pk9t4wwnFBXzAP_CKSVhS0p7m_FZG_8Q@mail.gmail.com>
On Mon, Nov 09, 2015 at 03:43:38PM +0530, punit vara wrote:
> On Mon, Nov 9, 2015 at 3:31 PM, glen lee <glen.lee@atmel.com> wrote:
> >
> >
> > On 2015년 11월 09일 18:05, punit vara wrote:
> >>
> >> On Mon, Nov 9, 2015 at 2:25 PM, glen lee <glen.lee@atmel.com> wrote:
> >>>
> >>> On 2015년 11월 09일 17:18, Dan Carpenter wrote:
> >>>>
> >>>> On Mon, Nov 09, 2015 at 05:02:48PM +0900, glen lee wrote:
> >>>>>
>
> make ./drivers/staging/wilc1000/ this working fine for me
>
> but
>
> make ./drivers/staging/wilc1000/linux_wlan.o is creates error.
I am also not getting build failure. Can you please post your .config file.
regards
sudip
next prev parent reply other threads:[~2015-11-09 10:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-08 21:31 [PATCH V2] Staging: wilc1000: Fix build break due to undeclared *wilc and implicit declaration of init_irq Punit Vara
2015-11-08 21:59 ` Dan Carpenter
2015-11-09 2:03 ` glen lee
2015-11-09 8:02 ` glen lee
2015-11-09 8:18 ` Dan Carpenter
2015-11-09 8:51 ` punit vara
2015-11-09 8:55 ` glen lee
2015-11-09 9:05 ` punit vara
2015-11-09 10:01 ` glen lee
2015-11-09 10:13 ` punit vara
2015-11-09 10:23 ` Sudip Mukherjee [this message]
2015-11-09 14:39 ` punit vara
2015-11-13 14:18 ` Sudip Mukherjee
2015-12-02 3:09 ` punit vara
2015-12-02 7:00 ` Sudip Mukherjee
2015-12-02 7:31 ` punit vara
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=20151109102342.GA3868@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=austin.shin@atmel.com \
--cc=chris.park@atmel.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=glen.lee@atmel.com \
--cc=gregkh@linuxfoundation.org \
--cc=johnny.kim@atmel.com \
--cc=leo.kim@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=punitvara@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