Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sameo@linux.intel.com (Samuel Ortiz)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Device Tree fixes for v3.9
Date: Mon, 11 Mar 2013 15:51:46 +0100	[thread overview]
Message-ID: <20130311145146.GA11450@zurbaran> (raw)
In-Reply-To: <201303111443.21019.arnd@arndb.de>

Hi Arnd,

On Mon, Mar 11, 2013 at 02:43:20PM +0000, Arnd Bergmann wrote:
> On Saturday 02 March 2013, Lee Jones wrote:
> > > 
> > > 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.
> 
> I've come up with the trivial patch below. I'm trying hard to kill off all known
> warnings, and will not take submissions introducing new ones if I see them.
> 
> Maybe Sam can just pick this up along with the other patch.
I'll take it.



> > > 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/
> 
> It hasn't made it into v3.9-rc2 or even linux-next yet. I guess it got lost
> somewhere.
In my Inbox. I'm planning to send a pull request to Linus later this week.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

  reply	other threads:[~2013-03-11 14:51 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
2013-03-11 14:43     ` Arnd Bergmann
2013-03-11 14:51       ` Samuel Ortiz [this message]
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=20130311145146.GA11450@zurbaran \
    --to=sameo@linux.intel.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