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 build failures
Date: Thu, 28 Feb 2013 13:51:39 -0800	[thread overview]
Message-ID: <20130228215138.GJ1622@atomide.com> (raw)
In-Reply-To: <1362077583-11184-1-git-send-email-linux@roeck-us.net>

Hi,

* Guenter Roeck <linux@roeck-us.net> [130228 11:21]:
> Commit c1d1cd59 (omap_device: remove obsolete pm_lats and early_device code)
> changed the number of parameters to omap_device_build(), but did not fix all
> calling code correctly. This causes build failures with some configurations.
> 
> arch/arm/mach-omap2/devices.c: In function 'omap_init_hdmi_audio':
> arch/arm/mach-omap2/devices.c:429:2: error: too many arguments to function 'omap_device_build'
> arch/arm/mach-omap2/omap_device.h:74:25: note: declared here
> make[2]: [arch/arm/mach-omap2/devices.o] Error 1 (ignored)
> arch/arm/mach-omap2/sr_device.c: In function 'sr_dev_init':
> arch/arm/mach-omap2/sr_device.c:155:2: error: too many arguments to function 'omap_device_build'
> arch/arm/mach-omap2/omap_device.h:74:25: note: declared here
> make[2]: [arch/arm/mach-omap2/sr_device.o] Error 1 (ignored)
> arch/arm/mach-omap2/am35xx-emac.c: In function 'omap_davinci_emac_dev_init':
> arch/arm/mach-omap2/am35xx-emac.c:66:6: error: too many arguments to function 'omap_device_build'
> arch/arm/mach-omap2/omap_device.h:74:25: note: declared here

Thanks, we already have a fix for this in linux next as
commit 6efc3fe0 (ARM: OMAP2+: fix some omap_device_build() calls that
aren't compiled by default). It seems that it will get sent today as
part of the rest of the arm-soc late branches.

Regards,

Tony

      reply	other threads:[~2013-02-28 21:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28 18:53 [PATCH] arm/omap2: Fix build failures Guenter Roeck
2013-02-28 21:51 ` 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=20130228215138.GJ1622@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).