From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Ux500 pin changes
Date: Thu, 15 Nov 2012 11:48:57 +0000 [thread overview]
Message-ID: <201211151148.57546.arnd@arndb.de> (raw)
In-Reply-To: <20121115112032.GB21682@gmail.com>
On Thursday 15 November 2012, Lee Jones wrote:
> On Thu, 15 Nov 2012, Linus Walleij wrote:
>
> > On Mon, Nov 12, 2012 at 11:35 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> >
> > > u8500_defconfig now gives me two new errors in arm-soc/for-next when building with
> > > -Werror:
> > >
> > > arch/arm/mach-ux500/board-mop500-pins.c:73:22: error: 'out_hi_wkup_pdis' defined but not used [-Werror=unused-variable]
> >
> > I've sent a fix for this, could you apply that patch directly to the
> > drivers branch?
> >
> > > and the existing:
> > >
> > > ERROR (phandle_references): Reference to non-existent node or label "tc3589x_gpio"
> > >
> > > Can you provide patches to fix these up?
> >
> > What on earth is that? Lee, do you know how to fix this one up, I shamelessly
> > assume it to be related to commit:
> > commit 3113e679021a3a6bace1c62a8432cc0ec27c09ab
> > "gpio: Enable the tc3298x GPIO expander driver for Device Tree"
>
> I haven't seen this error.
>
> Which kernel is this? How do I reproduce?
>
It's currently in arm-soc/for-next. Reproduce with "make u8500_defconfig && make".
I haven't bisected the problem, but it's obvious that some dts files reference
the "tc3589x_gpio" file that is not defined anywhere.
Arnd
prev parent reply other threads:[~2012-11-15 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 8:28 [GIT PULL] Ux500 pin changes Linus Walleij
2012-11-12 21:37 ` Arnd Bergmann
2012-11-12 22:35 ` Arnd Bergmann
2012-11-15 10:49 ` Linus Walleij
2012-11-15 11:20 ` Lee Jones
2012-11-15 11:48 ` Arnd Bergmann [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=201211151148.57546.arnd@arndb.de \
--to=arnd@arndb.de \
--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 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.