From: Arnd Bergmann <arnd@arndb.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
linus.walleij@stericsson.com, srinidhi.kasagar@stericsson.com,
linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org,
linux-next@vger.kernel.org, arm@kernel.org
Subject: Re: ARM: fix build failure on ux500 in linux-next
Date: Mon, 19 Mar 2012 08:57:23 +0000 [thread overview]
Message-ID: <201203190857.23489.arnd@arndb.de> (raw)
In-Reply-To: <CACRpkdYzS=wkfUU4gJLTp7djd6J20zVCC_6XhrjwoVpAoSe8iA@mail.gmail.com>
On Sunday 18 March 2012, Linus Walleij wrote:
> On Fri, Mar 16, 2012 at 10:18 PM, Paul Gortmaker
> <paul.gortmaker@windriver.com> wrote:
>
> > When I 1st saw this build failure, I thought it was me, because of the
> > BUG() stuff. But git bisect claims it comes from the arm-soc tree?
>
> Hm yeah looks like that, but we cannot see which commit
> I guess, just that it's the merge from ARM SoC?
>
> > In any case, the fix is trivial and self evident, regardless of where
> > it came from. I can carry it in my bug-3.4 cleanup tree if need be.
> > Let me know if you want me to do that.
>
> Any way that solves the issue is fine with me, maybe Arnd/Olof
> wants to apply it to the ARM SoC tree rather? If they don't say
> anything, by all means please keep it in cleanup.
As Lee commented, it should be fixed already with Marc's fixup patch.
Paul, if you still see it in some configuration on the today's linux-next,
please let us know.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: fix build failure on ux500 in linux-next
Date: Mon, 19 Mar 2012 08:57:23 +0000 [thread overview]
Message-ID: <201203190857.23489.arnd@arndb.de> (raw)
In-Reply-To: <CACRpkdYzS=wkfUU4gJLTp7djd6J20zVCC_6XhrjwoVpAoSe8iA@mail.gmail.com>
On Sunday 18 March 2012, Linus Walleij wrote:
> On Fri, Mar 16, 2012 at 10:18 PM, Paul Gortmaker
> <paul.gortmaker@windriver.com> wrote:
>
> > When I 1st saw this build failure, I thought it was me, because of the
> > BUG() stuff. But git bisect claims it comes from the arm-soc tree?
>
> Hm yeah looks like that, but we cannot see which commit
> I guess, just that it's the merge from ARM SoC?
>
> > In any case, the fix is trivial and self evident, regardless of where
> > it came from. I can carry it in my bug-3.4 cleanup tree if need be.
> > Let me know if you want me to do that.
>
> Any way that solves the issue is fine with me, maybe Arnd/Olof
> wants to apply it to the ARM SoC tree rather? If they don't say
> anything, by all means please keep it in cleanup.
As Lee commented, it should be fixed already with Marc's fixup patch.
Paul, if you still see it in some configuration on the today's linux-next,
please let us know.
Arnd
next prev parent reply other threads:[~2012-03-19 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 21:18 ARM: fix build failure on ux500 in linux-next Paul Gortmaker
2012-03-16 21:18 ` Paul Gortmaker
2012-03-18 23:19 ` Linus Walleij
2012-03-18 23:19 ` Linus Walleij
2012-03-19 8:57 ` Arnd Bergmann [this message]
2012-03-19 8:57 ` 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=201203190857.23489.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=paul.gortmaker@windriver.com \
--cc=srinidhi.kasagar@stericsson.com \
/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.