From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Joe Perches <joe@perches.com>
Subject: Re: linux-next: Tree for Feb 27 (microblaze build failure)
Date: Fri, 27 Feb 2015 11:59:58 -0800 [thread overview]
Message-ID: <20150227195958.GA13445@roeck-us.net> (raw)
In-Reply-To: <20150227154917.6d285971@canb.auug.org.au>
On Fri, Feb 27, 2015 at 03:49:17PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150226:
>
> New Tree: rpi
>
> The drm-intel tree gained a conflict against the drm-intel-fixes tree.
>
> The rcu tree gained a build failure so I used the version from
> next-20150226.
>
> The clk tree lost its build failure but gained another so I used the
> version from next-20150225.
>
> Non-merge commits (relative to Linus' tree): 1432
> 1565 files changed, 41138 insertions(+), 36333 deletions(-)
>
> ----------------------------------------------------------------------------
>
Building microblaze:mmu_defconfig ... failed
--------------
Error log:
arch/microblaze/kernel/cpu/mb.c: In function 'show_cpuinfo':
arch/microblaze/kernel/cpu/mb.c:105:2: error: 'x' undeclared (first use in this
function)
x seq_puts(m, "Icache:\t\tno\n");
^
Joe Perches' fat fingers are to blame for that one.
Guenter
next prev parent reply other threads:[~2015-02-27 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 4:49 linux-next: Tree for Feb 27 Stephen Rothwell
2015-02-27 19:59 ` Guenter Roeck [this message]
2015-02-27 22:39 ` linux-next: Tree for Feb 27 (microblaze build failure) Joe Perches
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=20150227195958.GA13445@roeck-us.net \
--to=linux@roeck-us.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).