From: Hollis Blanchard <hollisb@us.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: linux-next: kvm tree build failure
Date: Sun, 04 Jan 2009 13:45:47 -0600 [thread overview]
Message-ID: <1231098347.7724.11.camel@localhost.localdomain> (raw)
In-Reply-To: <49609896.201@redhat.com>
On Sun, 2009-01-04 at 13:08 +0200, Avi Kivity wrote:
> Stephen Rothwell wrote:
> > And again. Can you please find some fix for this so that the kvm tree
> > can get some integration testing ...
> >
>
> Hollis, help!
The "disarm" patch should fix the build. I'll resend that in a moment.
I'd like to remind you though that the cause of this breakage was the
debug patches you applied. It's also worth noting that the "fix" is to
delete functionality, so any way you look at it it's not a good
situation.
Between that and other kernel breakage (like Rusty's
smp_call_function_many patch), it has taken a lot of effort just to try
to catch up.
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2009-01-04 19:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 13:25 linux-next: kvm tree build failure Stephen Rothwell
2008-12-29 5:17 ` Stephen Rothwell
2009-01-02 0:53 ` Stephen Rothwell
2009-01-04 11:08 ` Avi Kivity
2009-01-04 19:45 ` Hollis Blanchard [this message]
2009-01-04 19:55 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2010-01-19 1:42 Stephen Rothwell
2010-01-19 7:57 ` Avi Kivity
2010-01-19 9:42 ` Stephen Rothwell
2010-01-11 8:07 Stephen Rothwell
2010-01-11 8:21 ` Stephen Rothwell
2010-01-11 10:27 ` Avi Kivity
2009-08-13 2:58 Stephen Rothwell
2009-08-13 8:58 ` Avi Kivity
2009-06-23 5:53 Stephen Rothwell
2009-06-23 10:23 ` Avi Kivity
2009-06-18 1:11 Stephen Rothwell
2009-06-18 4:25 ` Jaswinder Singh Rajput
2009-06-18 9:49 ` Avi Kivity
2009-05-21 7:21 Stephen Rothwell
2009-05-21 7:32 ` Avi Kivity
2009-05-21 7:37 ` Boaz Harrosh
2009-05-21 7:39 ` Avi Kivity
2009-05-21 7:48 ` Boaz Harrosh
2009-05-21 10:05 ` Avi Kivity
2008-12-18 11:05 Stephen Rothwell
2008-10-15 5:47 Stephen Rothwell
2008-10-15 13:25 ` Avi Kivity
2008-09-17 7:01 Stephen Rothwell
2008-09-17 8:50 ` Ingo Molnar
2008-09-24 12:39 ` Avi Kivity
2008-09-24 16:18 ` Jesse Barnes
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=1231098347.7724.11.camel@localhost.localdomain \
--to=hollisb@us.ibm.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--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).