From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/2] omap board removal for some omap3 boards for v3.13 merge window
Date: Fri, 18 Oct 2013 10:18:40 -0700 [thread overview]
Message-ID: <20131018171839.GR15154@atomide.com> (raw)
In-Reply-To: <CAGa+x87ykteWQ_T_-q6ANnPa4yCD3EF1uBKZ-hRYaPTJh_7x0A@mail.gmail.com>
* Kevin Hilman <khilman@linaro.org> [131018 10:14]:
> On Fri, Oct 18, 2013 at 8:24 AM, Tony Lindgren <tony@atomide.com> wrote:
> > * Kevin Hilman <khilman@linaro.org> [131018 07:49]:
> >> Hi Tony,
> >>
> >> Tony Lindgren <tony@atomide.com> writes:
> >>
> >> > The following changes since commit f41509ad0d4c11d0911630440749d409ce2aa1aa:
> >> >
> >> > Merge branches 'omap-for-v3.13/dt' and 'omap-for-v3.13/quirk' into omap-for-v3.13/board-removal (2013-10-14 11:33:07 -0700)
> >> >
> >> > are available in the git repository at:
> >> >
> >> >
> >> > git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.13/board-removal-signed
> >> >
> >> > for you to fetch changes up to f0c09b7c3b4e6b2fe501b3e888797b470de8320c:
> >> >
> >> > ARM: OMAP2+: Remove legacy support for zoom platforms (2013-10-15 17:38:21 -0700)
> >> >
> >> > ----------------------------------------------------------------
> >> > Changes needed to drop legacy booting support for some
> >> > omap3 boards.
> >> >
> >> > Note that that these are based on a merge of the
> >> > following for the dependencies:
> >> >
> >> > - v3.12-rc5 for fixes to pinctrl mask
> >> > - omap-for-v3.13/dt-signed to avoid pointless merge conflicts
> >> > - omap-for-v3.13/quirk-signed for legacy pdata handling
> >> >
> >> > ----------------------------------------------------------------
> >> > Aaro Koskinen (2):
> >> > ARM: dts: add minimal DT support for Nokia N950 & N9 phones
> >> > ARM: OMAP2: delete board-rm680
> >> >
> >> > Tony Lindgren (6):
> >> > ARM: dts: Shared file for omap GPMC connected smsc911x
> >> > ARM: dts: Add common support for omap3-evm
> >> > ARM: dts: Add basic support for TMDSEVM3730 (Mistral AM/DM37x EVM)
> >> > ARM: dts: Add basic support for zoom3
> >>
> >> This patch introduces a build failure when compiling the DTBs:
> >>
> >> [...]
> >> DTC arch/arm/boot/dts/omap3-zoom3.dtb
> >> ERROR (phandle_references): Reference to non-existent node or label "wl12xx_gpio"
> >
> > Oops sorry, looks like the common support for omap3-evm has a
> > pinctrl entry that should be in the omap3-evm-37xx only. I guess
> > I did not run make dtbs after adding the omap3-evm-37xx parts.
> > The patch below fixes it for me.
> >
> > Do you want a new pull request or just the fix below?
>
> Thanks for the fix.
>
> I'd prefer a new pull req so we don't have a broken build in the
> middle of the series.
OK will apply Javier's patch also and send a new pull req.
Regards,
Tony
next prev parent reply other threads:[~2013-10-18 17:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <526041db.41abe00a.33b7.00a1SMTPIN_ADDED_BROKEN@mx.google.com>
2013-10-18 14:48 ` [GIT PULL 1/2] omap board removal for some omap3 boards for v3.13 merge window Kevin Hilman
2013-10-18 15:24 ` Tony Lindgren
2013-10-18 15:45 ` Javier Martinez Canillas
2013-10-18 15:53 ` Tony Lindgren
2013-10-18 17:13 ` Kevin Hilman
2013-10-18 17:18 ` Tony Lindgren [this message]
2013-10-17 20:00 Tony Lindgren
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=20131018171839.GR15154@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).