From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: ux500: Fix build error caused by recent variable name change
Date: Fri, 27 Apr 2012 20:53:40 +0100 [thread overview]
Message-ID: <4F9AF944.5090309@linaro.org> (raw)
In-Reply-To: <CACRpkdaRdn+q2ODUir6dE8btB8+RTkCYsN0W-Zsj7mkRDNrHQw@mail.gmail.com>
On 27/04/12 18:48, Linus Walleij wrote:
> On Fri, Apr 27, 2012 at 5:36 PM, Lee Jones<lee.jones@linaro.org> wrote:
>
>> error: ?u8500_soc_node? undeclared (first use in this function)
>>
>> Was recently changed to 'u8500_local_bus_nodes'.
>>
>> Signed-off-by: Lee Jones<lee.jones@linaro.org>
>
> IIRC I already fixed this up when applying the patch renaming the node.
>
> Can you check the ux500-core branch on my linux-stericsson tree?
Just did.
Seemingly the patch was complete after all (I could have sworn that I
tested it). I have no idea how I lost it from my own tree though.
Scrap this then.
/Lee
prev parent reply other threads:[~2012-04-27 19:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 15:36 [PATCH] ARM: ux500: Fix build error caused by recent variable name change Lee Jones
2012-04-27 17:48 ` Linus Walleij
2012-04-27 19:53 ` Lee Jones [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=4F9AF944.5090309@linaro.org \
--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).