From: Guenter Roeck <linux@roeck-us.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Lutomirski <luto@amacapital.net>,
James Hogan <james.hogan@imgtec.com>,
linux-metag@vger.kernel.org
Subject: Re: linux-next: Tree for Dec 16
Date: Mon, 15 Dec 2014 22:55:02 -0800 [thread overview]
Message-ID: <548FD746.1050904@roeck-us.net> (raw)
In-Reply-To: <20141215224444.dc7f0f3c.akpm@linux-foundation.org>
On 12/15/2014 10:44 PM, Andrew Morton wrote:
> On Mon, 15 Dec 2014 22:35:49 -0800 Guenter Roeck <linux@roeck-us.net> wrote:
>
>> On Tue, Dec 16, 2014 at 03:46:22PM +1100, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Please do not add any code destined for v3.20 to your linux-next included
>>> trees/branches until after v3.19-rc1 is released.
>>>
>>> Changes since 20141215:
>>>
>>> The infiniband tree gained a conflict against Linus' tree and a build
>>> failure so I used the version from next-20141215.
>>>
>>> The userns tree gained a conflict against the vfs tree.
>>>
>>> The clk tree gained a build failure so I used the version from
>>> next-20141215.
>>>
>>> Non-merge commits (relative to Linus' tree): 3588
>>> 2582 files changed, 123494 insertions(+), 135748 deletions(-)
>>>
>>
>> My metag buildbot test fails with this kernel.
>
> Thanks. What are the error messages?
>
>
Nothing. It just hangs until killed.
qemu log:
char device redirected to /dev/pts/5
Unable to load ROM!
qemu: terminating on signal 15 from pid 17843
http://server.roeck-us.net:8010/builders/qemu-metag-next/builds/60/steps/qemubuildcommand/logs/stdio
Normally output would be similar to the following.
/opt/buildbot/bin/qemu-system-meta -display none -kernel vmlinux -device da,exit_threads=1 -chardev stdio,id=chan1 -chardev pty,id=chan2 -append "rdinit=/sbin/init"
char device redirected to /dev/pts/29
Unable to load ROM!
Linux version 3.18.0+ (groeck@server.roeck-us.net) (gcc version 4.2.4 (IMG-1.4.0.300)) #5 Mon Dec 15 22:50:31 PST 2014
LNKGET/SET go through cache but CONFIG_METAG_LNKGET_AROUND_CACHE=y
DA present
...
Guenter
next prev parent reply other threads:[~2014-12-16 6:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 4:46 linux-next: Tree for Dec 16 Stephen Rothwell
2014-12-16 6:35 ` Guenter Roeck
2014-12-16 6:44 ` Andrew Morton
2014-12-16 6:55 ` Guenter Roeck [this message]
2014-12-16 9:42 ` James Hogan
2014-12-16 10:45 ` James Hogan
2014-12-16 23:57 ` Stephen Rothwell
2014-12-17 0:08 ` Andrew Morton
2014-12-17 0:23 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2025-12-16 1:47 Stephen Rothwell
2024-12-16 6:25 Stephen Rothwell
2022-12-16 1:46 Stephen Rothwell
2020-12-16 9:40 Stephen Rothwell
2019-12-16 5:22 Stephen Rothwell
2016-12-16 3:49 Stephen Rothwell
2015-12-16 5:43 Stephen Rothwell
2013-12-16 5:59 Stephen Rothwell
2011-12-16 6:00 Stephen Rothwell
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=548FD746.1050904@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-metag@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=luto@amacapital.net \
--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