From: Samuel Ortiz <sameo@linux.intel.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] mfd: asic3: Fix build error
Date: Mon, 18 Apr 2011 10:58:20 +0200 [thread overview]
Message-ID: <20110418085819.GC8593@sortiz-mobl> (raw)
In-Reply-To: <1302792227.8637.2.camel@phoenix>
Hi Axel,
On Thu, Apr 14, 2011 at 10:43:47PM +0800, Axel Lin wrote:
> Fix below compile error:
>
> CC drivers/mfd/asic3.o
> drivers/mfd/asic3.c: In function 'asic3_irq_demux':
> drivers/mfd/asic3.c:147: error: 'irq_data' undeclared (first use in this function)
> drivers/mfd/asic3.c:147: error: (Each undeclared identifier is reported only once
> drivers/mfd/asic3.c:147: error: for each function it appears in.)
I wonder how this one got through...
I applied it to my for-linus branch anyway. Thanks a lot.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2011-04-18 8:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 14:43 [PATCH] mfd: asic3: Fix build error Axel Lin
2011-04-18 8:58 ` Samuel Ortiz [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=20110418085819.GC8593@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=axel.lin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).