From: punit vara <punitvara@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, chris.park@atmel.com,
Austin Shin <austin.shin@atmel.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
johnny.kim@atmel.com, tony.cho@atmel.com, leo.kim@atmel.com
Subject: Re: [PATCH] Staging: wilc1000: Fix build break due to undeclared *wilc and implicit declaration of init_irq
Date: Sun, 8 Nov 2015 20:47:00 +0530 [thread overview]
Message-ID: <CABXAfNJCcw0G9BM_mT6SLXxDjE6ifhM-AsVt6fy8WUE7eX4=3A@mail.gmail.com> (raw)
In-Reply-To: <20151107205101.GK18797@mwanda>
On Sun, Nov 8, 2015 at 2:21 AM, Dan Carpenter <dan.carpenter@oracle.com> wrote:
> I haven't looked at it, sorry. You'll have to figure it out or if you
> complain to the original person who broken the build he can figure it
> out. You are still missing a Fixes tag.
>
> regards,
> dan carpenter
Actually while building one of my another patch I have found this
broken. Now I understand what tag is . Would you tell me how can I
find that particular commit which create defeat in this file ? Sorry
first time I have encounter this kind of problem so I do not know how
to figure it out.
prev parent reply other threads:[~2015-11-08 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 11:31 [PATCH] Staging: wilc1000: Fix build break due to undeclared *wilc and implicit declaration of init_irq Punit Vara
2015-11-07 13:54 ` Dan Carpenter
2015-11-07 18:14 ` punit vara
2015-11-07 20:51 ` Dan Carpenter
2015-11-08 13:53 ` punit vara
2015-11-08 15:17 ` punit vara [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='CABXAfNJCcw0G9BM_mT6SLXxDjE6ifhM-AsVt6fy8WUE7eX4=3A@mail.gmail.com' \
--to=punitvara@gmail.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-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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.