From: Jon Hunter <jon-hunter@ti.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnd Bergmann <arnd@arndb.de>, Tony Lindgren <tony@atomide.com>,
linux-next@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Belisko Marek <marek.belisko@gmail.com>,
Olof Johansson <olof@lixom.net>,
Nathan Fontenot <nfont@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: omap2plus_defconfig fails to build
Date: Mon, 3 Dec 2012 17:38:34 -0600 [thread overview]
Message-ID: <50BD37FA.2090501@ti.com> (raw)
In-Reply-To: <20121204102631.3d8d41e3e8a8c0eb71734e55@canb.auug.org.au>
Hi Stephen,
On 12/03/2012 05:26 PM, Stephen Rothwell wrote:
> Hi all,
>
> On Thu, 29 Nov 2012 11:40:18 +0100 Belisko Marek <marek.belisko@gmail.com> wrote:
>>
>> I've update linux-next to next-20121129 and omap2plus_defconfig fails to build:
>> arch/arm/mach-omap2/timer.c: In function 'omap_get_timer_dt':
>> arch/arm/mach-omap2/timer.c:195: error: implicit declaration of
>> function 'prom_add_property'
>
> Caused by commit 9725f4451a9c ("ARM: OMAP: Add DT support for timer
> driver") from the arm-soc tree interacting with commit 79d1c712958f
> ("powerpc+of: Rename the drivers/of prom_* functions to of_*") from the
> powerpc tree.
>
> I will fix this up in today' linux-next (by changing prom_add_property to
> of_add_property). Someone will need to remember to tell Linus when the
> latter of those two commits gets merged.
Just to let you know there is a patch available for this problem [1].
Tony, Olof, Arnd, not sure how you guys wish to handle this one.
Cheers
Jon
[1] http://www.spinics.net/lists/arm-kernel/msg210179.html
next prev parent reply other threads:[~2012-12-03 23:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAfyv37BA4YMRFJsN5n7EeAD7iE3hzQ2PDqBAtqCju7JdxrvTA@mail.gmail.com>
2012-12-03 23:26 ` omap2plus_defconfig fails to build Stephen Rothwell
2012-12-03 23:38 ` Jon Hunter [this message]
2012-12-04 0:05 ` Stephen Rothwell
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=50BD37FA.2090501@ti.com \
--to=jon-hunter@ti.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=marek.belisko@gmail.com \
--cc=nfont@linux.vnet.ibm.com \
--cc=olof@lixom.net \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
--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;
as well as URLs for NNTP newsgroup(s).