linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2+: Fix compillation error in mach-omap2/timer.c
Date: Wed, 19 Dec 2012 08:38:56 -0800	[thread overview]
Message-ID: <20121219163856.GN4989@atomide.com> (raw)
In-Reply-To: <B5906170F1614E41A8A28DE3B8D121433EC9A56D@DBDE01.ent.ti.com>

* Bedia, Vaibhav <vaibhav.bedia@ti.com> [121219 02:18]:
> Hi Peter, Tony
> 
> On Wed, Dec 19, 2012 at 15:20:09, Ujfalusi, Peter wrote:
> > prom_add_property() has been renamed to of_add_property()
> > This patch fixes the following comilation error:
> > 
> > arch/arm/mach-omap2/timer.c: In function ?omap_get_timer_dt?:
> > arch/arm/mach-omap2/timer.c:178:3: error: implicit declaration of function ?prom_add_property? [-Werror=implicit-function-declaration]
> > cc1: some warnings being treated as errors
> > make[1]: *** [arch/arm/mach-omap2/timer.o] Error 1
> > make[1]: *** Waiting for unfinished jobs....
> > 
> > Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> > ---
> > Hi Tony,
> > 
> > today's mainline does not compile due to this API rename in of core.
> > Not sure if we alreasy have fix for this pending.
> > 

Thanks applying.
 
> There following patches for needed to get omap2plus_defconfig build working
> 
> https://patchwork.kernel.org/patch/1810481/ - address the build breakage due to header file cleanup
> https://patchwork.kernel.org/patch/1810441/ - address the prom_add_property() issue
> http://marc.info/?l=linux-arm-kernel&m=135589966017628&w=2 - this crept in during a merge commit.

Thanks all these should be queued up somewhere now.

Regards,

Tony 

      reply	other threads:[~2012-12-19 16:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-19  9:50 [PATCH] ARM: OMAP2+: Fix compillation error in mach-omap2/timer.c Peter Ujfalusi
2012-12-19 10:16 ` Bedia, Vaibhav
2012-12-19 16:38   ` Tony Lindgren [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=20121219163856.GN4989@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).