linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Device Tree fixes for v3.9
Date: Sat, 2 Mar 2013 08:58:52 +0800	[thread overview]
Message-ID: <20130302005852.GA3106@gmail.com> (raw)
In-Reply-To: <201303012319.28231.arnd@arndb.de>

On Fri, 01 Mar 2013, Arnd Bergmann wrote:

> On Friday 01 March 2013, Linus Walleij wrote:
> > Hi Olof, Arnd,
> > 
> > Here is a pull request for the Device Tree fixes for Ux500 in the v3.9 series.
> > 
> > Basically this should have come in earlier, but I failed at processing
> > it in time
> > for the merge window. t should have been this cycle's Ux500 DT topic branch.
> > 
> > As discussed I've started to funnel all Ux500 DT stuff through my ux500 tree
> > in order to do some coordination and I became overloaded. So this patch set
> > got stuck in the air. It was not trivial to push since this branch had a few
> > conflicts with other branches. (There might have been a good way to solve
> > that but I didn't come up with it in time.)
> > 
> > Basically how to handle it is your pick, in the old times I would have pushed
> > it ASAP, maybe during -rc1, as it restores the Ux500 DT to a working state
> > for the basic functionality (notably ethernet and MMC on the Snowball).
> > 
> > Please pull it in, for fixes or -next at your decision. As you can see the
> > base is at Torvald's HEAD since all dependencies that conflicted with
> > this branch is now there. If you want me to resend based on v3.9-rc1
> > or so, just tell.
> 
> 
> I'm still getting build errors even with those patches applied:
> 
> Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1)
> Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1)
> Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1)
> Warning (reg_format): "reg" property in /soc-u9500/prcmu at 80157000/ab8500 at 5 has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1)

These have been there since DT landed for the AB8500 - it's on my TODO
to fix, but it's a really low priority.

> drivers/built-in.o: In function `ab8500_power_off':
> /git/arm-soc/drivers/mfd/ab8500-sysctrl.c:37: undefined reference to `power_supply_get_by_name'
> /git/arm-soc/drivers/mfd/ab8500-sysctrl.c:53: undefined reference to `power_supply_get_by_name'
> make[2]: *** [vmlinux] Error 1

This has already been fixed.

https://patchwork.kernel.org/patch/2163301/

-- 
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2013-03-02  0:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-01 23:06 [GIT PULL] Device Tree fixes for v3.9 Linus Walleij
2013-03-01 23:19 ` Arnd Bergmann
2013-03-02  0:58   ` Lee Jones [this message]
2013-03-11 14:43     ` Arnd Bergmann
2013-03-11 14:51       ` Samuel Ortiz
2013-03-11 15:20         ` Arnd Bergmann
2013-03-13  8:37       ` Samuel Ortiz
2013-03-13 18:01         ` Arnd Bergmann
2013-03-15 21:25 ` Arnd Bergmann
2013-03-15 22:18   ` Arnd Bergmann

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=20130302005852.GA3106@gmail.com \
    --to=lee.jones@linaro.org \
    --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).