public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
	Jaswinder Singh Rajput <jaswinderlinux@gmail.com>,
	Sam Ravnborg <sam@ravnborg.org>, Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	x86 maintainers <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL -tip v3] fix 39 'make headers_check' warnings
Date: Wed, 04 Feb 2009 19:22:14 +0200	[thread overview]
Message-ID: <4989CEC6.5040502@redhat.com> (raw)
In-Reply-To: <200902041737.57453.arnd@arndb.de>

Arnd Bergmann wrote:
> On Wednesday 04 February 2009, Jaswinder Singh Rajput wrote:
>   
>> On Wed, 2009-02-04 at 17:40 +0200, Avi Kivity wrote:
>>     
>>> If there's such a patch in the URL you posted, please point to it directly.
>>>
>>>       
>> All CONFIG_* patches are dropped.
>>     
>
> Well, the kvm.h patch was one of two that AFAICT are actually needed:
> If you don't define CONFIG_X86 or CONFIG_IA64 in user space, you
> won't see the definitions for kvm_irqchip->pic, kvm_irqchip->ioapic
> or KVM_CAP_{DEVICE_ASSIGNMENT,DEVICE_MSI,USER_MSI}.
>   

I have a fix for that queued.


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


      reply	other threads:[~2009-02-04 17:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-18 14:04 [GIT PULL -tip v3] fix 39 'make headers_check' warnings Jaswinder Singh Rajput
2009-01-18 17:28 ` Ingo Molnar
2009-01-18 18:50   ` Ingo Molnar
2009-01-18 18:52     ` Ingo Molnar
2009-01-18 19:08     ` Sam Ravnborg
2009-01-18 19:09       ` Ingo Molnar
2009-01-18 19:45         ` Sam Ravnborg
2009-01-19  2:16       ` Jaswinder Singh Rajput
2009-01-19  5:27         ` Sam Ravnborg
2009-01-19  2:10     ` Jaswinder Singh Rajput
2009-01-19  2:20       ` Harvey Harrison
2009-01-19 11:15         ` Ingo Molnar
2009-01-19 18:08           ` Harvey Harrison
2009-01-18 18:56 ` Ingo Molnar
2009-01-19  9:19   ` Avi Kivity
2009-01-19 11:01     ` Sam Ravnborg
2009-01-19 11:53       ` Avi Kivity
2009-01-24  6:16         ` Jaswinder Singh Rajput
2009-02-04 14:28           ` Avi Kivity
2009-02-04 15:17             ` Jaswinder Singh Rajput
2009-02-04 15:40               ` Avi Kivity
2009-02-04 16:00                 ` Jaswinder Singh Rajput
2009-02-04 16:37                   ` Arnd Bergmann
2009-02-04 17:22                     ` 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=4989CEC6.5040502@redhat.com \
    --to=avi@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=jaswinder@kernel.org \
    --cc=jaswinderlinux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sam@ravnborg.org \
    --cc=x86@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