From: Avi Kivity <avi@redhat.com>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: 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 17:40:39 +0200 [thread overview]
Message-ID: <4989B6F7.4060004@redhat.com> (raw)
In-Reply-To: <1233760678.3180.2.camel@localhost.localdomain>
Jaswinder Singh Rajput wrote:
> On Wed, 2009-02-04 at 16:28 +0200, Avi Kivity wrote:
>
>> Jaswinder Singh Rajput wrote:
>>
>>> latest -tip is still giving 'make headers_check' warnings:
>>> usr/include/linux/kvm.h:61: leaks CONFIG_X86 to userspace where it is not valid
>>> usr/include/linux/kvm.h:64: leaks CONFIG_X86 to userspace where it is not valid
>>> usr/include/linux/kvm.h:387: leaks CONFIG_X86 to userspace where it
>>> is not valid
>>> usr/include/linux/kvm.h:391: leaks CONFIG_X86 to userspace where it
>>> is not valid
>>> usr/include/linux/kvm.h:396: leaks CONFIG_X86 to userspace where it
>>> is not valid
>>>
>>> So should I resend my patch or you are going to move this stuff
>>>
>>>
>> Your patch is broken. I'll push mine shortly.
>>
>>
>
> hmm. it seems you are looking at old patches which we already dropped.
>
> Please check the latest patches and kbuild at:
> http://git.kernel.org/?p=linux/kernel/git/mingo/linux-2.6-x86.git;a=shortlog;h=core/header-fixes
>
>
These are the <linux/types.h> patches. I was talking about the
CONFIG_X86 in the headers.
If there's such a patch in the URL you posted, please point to it directly.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-02-04 15:41 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 [this message]
2009-02-04 16:00 ` Jaswinder Singh Rajput
2009-02-04 16:37 ` Arnd Bergmann
2009-02-04 17:22 ` Avi Kivity
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=4989B6F7.4060004@redhat.com \
--to=avi@redhat.com \
--cc=akpm@linux-foundation.org \
--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