From: Kevin Hilman <khilman@ti.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: tony@atomide.com, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm: omap2: fix build failure
Date: Thu, 17 Nov 2011 11:36:33 -0800 [thread overview]
Message-ID: <87aa7u4k3i.fsf@ti.com> (raw)
In-Reply-To: <CACVXFVMtaiFiKSRh8geVpOzymtZsaUKc9tDHfgJYR57N+RQZ-g@mail.gmail.com> (Ming Lei's message of "Thu, 17 Nov 2011 11:00:18 +0800")
Ming Lei <tom.leiming@gmail.com> writes:
> On Wed, Nov 9, 2011 at 3:24 AM, Kevin Hilman <khilman@ti.com> wrote:
>> tom.leiming@gmail.com writes:
>>
>>> From: Ming Lei <tom.leiming@gmail.com>
>>>
>>> The patch fixes the compile failure:
>>>
>>> CC arch/arm/mach-omap2/cpuidle34xx.o
>>> arch/arm/mach-omap2/cpuidle34xx.c:317:12: error: 'THIS_MODULE'
>>> undeclared here (not in a function)
>>> make[1]: *** [arch/arm/mach-omap2/cpuidle34xx.o] Error 1
>>> make: *** [arch/arm/mach-omap2] Error 2
>>> make: *** Waiting for unfinished jobs....
>>>
>>> Signed-off-by: Ming Lei <tom.leiming@gmail.com>
>>
>> FYI...
>>
>> Tony has already queued fix for this in his fixes branch.
>>
>> http://marc.info/?l=linux-arm-kernel&m=132071036621713&w=2
>
> The fix is not merged into 3.2.0-rc2-next-20111116+ yet...
OK, but that doesn't mean you have to keep sending it. It just means
Tony's fixes branch isn't in -next (yet.)
Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-11-17 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 4:34 [PATCH] arm: omap2: fix build failure tom.leiming
2011-11-08 19:24 ` Kevin Hilman
2011-11-17 3:00 ` Ming Lei
2011-11-17 19:36 ` Kevin Hilman [this message]
2011-11-18 1:16 ` Ming Lei
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=87aa7u4k3i.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tom.leiming@gmail.com \
--cc=tony@atomide.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