From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Xen Devel <Xen-devel@lists.xensource.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Sheng Yang <sheng@linux.intel.com>, Dave McCracken <dcm@mccr.org>
Subject: Re: linux-next: build failure after merge of the final tree (xen tree related)
Date: Mon, 26 Jul 2010 12:47:24 -0700 [thread overview]
Message-ID: <4C4DE64C.9070004@goop.org> (raw)
In-Reply-To: <20100726152908.951a95b7.sfr@canb.auug.org.au>
On 07/25/2010 10:29 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (i386 defconfig)
> failed like this:
Both these build failures should be fixed in upstream/xen now.
Thanks,
J
next prev parent reply other threads:[~2010-07-26 19:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 5:29 linux-next: build failure after merge of the final tree (xen tree related) Stephen Rothwell
2010-07-26 5:29 ` Stephen Rothwell
2010-07-26 10:43 ` Stefano Stabellini
2010-07-26 17:25 ` Jeremy Fitzhardinge
2010-07-26 17:57 ` Stefano Stabellini
2010-07-26 18:14 ` Jeremy Fitzhardinge
2010-07-26 19:47 ` Jeremy Fitzhardinge [this message]
2010-07-27 0:01 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2010-07-26 5:10 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=4C4DE64C.9070004@goop.org \
--to=jeremy@goop.org \
--cc=Xen-devel@lists.xensource.com \
--cc=dcm@mccr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sheng@linux.intel.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.