From: Tony Lindgren <tony@atomide.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-next@vger.kernel.org
Subject: Re: [PATCH 1/3] arm: anticipate build breakages due in pending merge
Date: Mon, 5 Mar 2012 14:45:35 -0800 [thread overview]
Message-ID: <20120305224534.GG12083@atomide.com> (raw)
In-Reply-To: <1330987310-8108-2-git-send-email-paul.gortmaker@windriver.com>
* Paul Gortmaker <paul.gortmaker@windriver.com> [120305 14:10]:
> Testing in linux-next has revealed that the omap2plus_defconfig
> will fail upon the merge of "arm-soc/for-next" as follows:
>
> arch/arm/mach-omap2/control.c:238: error: 'OMAP343X_CTRL_BASE' undeclared (first use in this function)
> arch/arm/mach-omap2/common.c:48: error: 'OMAP2420_SDRC_BASE' undeclared here (not in a function)
> arch/arm/mach-omap2/common.c:49: error: 'OMAP2420_SMS_BASE' undeclared here (not in a function)
> arch/arm/mach-omap2/common.c:50: error: 'OMAP242X_CTRL_BASE' undeclared here (not in a function)
> [...]
> arch/arm/mach-omap2/common.c:167: error: 'OMAP4430_CM2_BASE' undeclared here (not in a function)
> arch/arm/mach-omap2/sdrc2xxx.c:108: error: 'OMAP2420_PRM_BASE' undeclared (first use in this function)
> arch/arm/mach-omap2/cm2xxx_3xxx.c:310: error: 'OMAP3430_CM_BASE' undeclared (first use in this function)
>
> It appears that a once implicit path to <plat/hardware.h> has gone
> away once two of the arm streams come together.
Thanks this one is already waiting to be applied to arm-soc
tree.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] arm: anticipate build breakages due in pending merge
Date: Mon, 5 Mar 2012 14:45:35 -0800 [thread overview]
Message-ID: <20120305224534.GG12083@atomide.com> (raw)
In-Reply-To: <1330987310-8108-2-git-send-email-paul.gortmaker@windriver.com>
* Paul Gortmaker <paul.gortmaker@windriver.com> [120305 14:10]:
> Testing in linux-next has revealed that the omap2plus_defconfig
> will fail upon the merge of "arm-soc/for-next" as follows:
>
> arch/arm/mach-omap2/control.c:238: error: 'OMAP343X_CTRL_BASE' undeclared (first use in this function)
> arch/arm/mach-omap2/common.c:48: error: 'OMAP2420_SDRC_BASE' undeclared here (not in a function)
> arch/arm/mach-omap2/common.c:49: error: 'OMAP2420_SMS_BASE' undeclared here (not in a function)
> arch/arm/mach-omap2/common.c:50: error: 'OMAP242X_CTRL_BASE' undeclared here (not in a function)
> [...]
> arch/arm/mach-omap2/common.c:167: error: 'OMAP4430_CM2_BASE' undeclared here (not in a function)
> arch/arm/mach-omap2/sdrc2xxx.c:108: error: 'OMAP2420_PRM_BASE' undeclared (first use in this function)
> arch/arm/mach-omap2/cm2xxx_3xxx.c:310: error: 'OMAP3430_CM_BASE' undeclared (first use in this function)
>
> It appears that a once implicit path to <plat/hardware.h> has gone
> away once two of the arm streams come together.
Thanks this one is already waiting to be applied to arm-soc
tree.
Regards,
Tony
next prev parent reply other threads:[~2012-03-05 22:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 22:41 [PATCH 0/3] arm: fix build breakage in omap2plus_defconfig (linux-next) Paul Gortmaker
2012-03-05 22:41 ` Paul Gortmaker
2012-03-05 22:41 ` [PATCH 1/3] arm: anticipate build breakages due in pending merge Paul Gortmaker
2012-03-05 22:41 ` Paul Gortmaker
2012-03-05 22:45 ` Tony Lindgren [this message]
2012-03-05 22:45 ` Tony Lindgren
2012-03-05 22:41 ` [PATCH 2/3] arm: fix compile error in mach-omap2/board-omap4panda.c Paul Gortmaker
2012-03-05 22:41 ` Paul Gortmaker
2012-03-05 22:46 ` Tony Lindgren
2012-03-05 22:46 ` Tony Lindgren
2012-03-06 11:03 ` Peter Ujfalusi
2012-03-06 11:03 ` Peter Ujfalusi
2012-03-05 22:41 ` [PATCH 3/3] arm: more fallout from i2c conversions in board-omap4panda.c Paul Gortmaker
2012-03-05 22:41 ` Paul Gortmaker
2012-03-06 12:27 ` Peter Ujfalusi
2012-03-06 12:27 ` Peter Ujfalusi
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=20120305224534.GG12083@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul.gortmaker@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.