From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: kgdb tree build failure
Date: Mon, 4 Jan 2010 16:44:52 +1100 [thread overview]
Message-ID: <20100104164452.2803d62e.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100104164209.a5ac8d6a.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 375 bytes --]
Hi Jason,
On Mon, 4 Jan 2010 16:42:09 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next build (arm realview_defconfig) failed like this:
^^^^^^^^^
Most of the other arm builds failed the same way ...
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-01-04 5:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 5:42 linux-next: kgdb tree build failure Stephen Rothwell
2010-01-04 5:44 ` Stephen Rothwell [this message]
2010-01-04 12:55 ` Jason Wessel
2010-01-04 13:04 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-12-24 0:56 Stephen Rothwell
2009-12-24 3:58 ` Jason Wessel
2009-12-24 12:18 ` Stephen Rothwell
2009-12-24 0:16 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=20100104164452.2803d62e.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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