From: "Jaswinder Singh Rajput" <jaswinderlinux@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Jiri Kosina" <jkosina@suse.cz>,
"Jeremy Fitzhardinge" <jeremy@goop.org>,
linux-kernel@vger.kernel.org,
"Jaswinder Singh Rajput" <jaswinderrajput@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: build breakage -- paravirt_{alloc,free}_ldt
Date: Mon, 12 Jan 2009 16:27:48 +0530 [thread overview]
Message-ID: <3f9a31f40901120257m27a9b047kd8dcee2793467bb3@mail.gmail.com> (raw)
In-Reply-To: <20090112105202.GF10405@elte.hu>
On Mon, Jan 12, 2009 at 4:22 PM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Jiri Kosina <jkosina@suse.cz> wrote:
>
>> Hi,
>>
>> with Linus' tree (ae04d14015) doesn't build for me with
>>
>> arch/x86/kernel/ldt.c: In function 'alloc_ldt':
>> arch/x86/kernel/ldt.c:55: error: implicit declaration of function 'paravirt_alloc_ldt'
>> arch/x86/kernel/ldt.c:79: error: implicit declaration of function 'paravirt_free_ldt'
>>
>> Config on http://www.jikos.cz/jikos/junk/.config
>
> hm, it builds fine here with your config. Did .28 build fine for you? The
> only change to this file since .28 has been Jaswinder's "423a540: x86:
> ldt.c fix style problems".
>
No, it is not because of my patch but I will check for the solution.
Thanks,
--
JSR
next prev parent reply other threads:[~2009-01-12 10:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 10:23 Jiri Kosina
2009-01-12 10:52 ` Ingo Molnar
2009-01-12 10:57 ` Jaswinder Singh Rajput [this message]
2009-01-12 11:08 ` Jaswinder Singh Rajput
2009-01-12 11:17 ` Ingo Molnar
2009-01-12 11:12 ` Jiri Kosina
2009-01-12 11:18 ` Ingo Molnar
2009-01-12 11:35 ` Jiri Kosina
2009-01-12 11:19 ` Jaswinder Singh Rajput
2009-01-12 11:24 ` Ingo Molnar
2009-01-12 11:36 ` Jaswinder Singh Rajput
2009-01-12 11:39 ` Ingo Molnar
2009-01-12 11:52 ` Jaswinder Singh Rajput
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=3f9a31f40901120257m27a9b047kd8dcee2793467bb3@mail.gmail.com \
--to=jaswinderlinux@gmail.com \
--cc=hpa@zytor.com \
--cc=jaswinderrajput@gmail.com \
--cc=jeremy@goop.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®