linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Valdis.Kletnieks@vt.edu
Cc: Beth Kon <eak@us.ibm.com>,
	rostedt@goodmis.org, Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Wierdness - linux-next KVM patch breaks Dell Latitude D820, KVM not in kernel
Date: Wed, 09 Sep 2009 17:25:17 +0300	[thread overview]
Message-ID: <4AA7BACD.2090601@redhat.com> (raw)
In-Reply-To: <22130.1252438888@turing-police.cc.vt.edu>

On 09/08/2009 10:41 PM, Valdis.Kletnieks@vt.edu wrote:
>
> Yeah, I was quite confused by the bisect results as well, I may end up
> re-doing it just to make sure I didn't screw something up along the way (since
> I started it with -rc7/HEAD as the good/bad, but most of the resulting
> kernels reported a pre-rc7 release (a 2.6.28 at one point, IIRC, and it
> finished at 31-rc2.
>    


This is normal, if a branch based on 2.6.28 was merged into 2.6.31-rc a 
bisect may detour through that branch and generate that version.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-09-09 14:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-07 14:07 Wierdness - linux-next KVM patch breaks Dell Latitude D820, KVM not in kernel Valdis.Kletnieks
2009-09-08 13:32 ` Beth Kon
2009-09-08 19:41   ` Valdis.Kletnieks
2009-09-09 14:25     ` Avi Kivity [this message]
2009-09-09 17:34     ` Valdis.Kletnieks
2009-09-09 17:38       ` Avi Kivity
2009-09-09 18:59         ` Valdis.Kletnieks
2009-09-12 20:55           ` Valdis.Kletnieks
2009-09-13 11:39             ` Avi Kivity
2009-09-20 15:50 ` Valdis.Kletnieks

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=4AA7BACD.2090601@redhat.com \
    --to=avi@redhat.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=eak@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).