From: Avi Kivity <avi@redhat.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: CONFIG_NO_BOOTMEM woes, 2.6.34-rc1
Date: Wed, 17 Mar 2010 12:28:52 +0200 [thread overview]
Message-ID: <4BA0AEE4.10209@redhat.com> (raw)
In-Reply-To: <4BA0AAC8.5000702@redhat.com>
On 03/17/2010 12:11 PM, Avi Kivity wrote:
>
> I reproduced this on x86_64 as well (both physical and virtual), fails
> earlier this time.
>
Sorry, that was with a crap printk.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-03-17 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 15:28 CONFIG_NO_BOOTMEM woes, 2.6.34-rc1 Avi Kivity
2010-03-15 17:52 ` Yinghai Lu
2010-03-17 10:11 ` Avi Kivity
2010-03-17 10:28 ` Avi Kivity [this message]
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=4BA0AEE4.10209@redhat.com \
--to=avi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yinghai@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