From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Jeff Dike <jdike@addtoit.com>
Cc: Christoph Lameter <clameter@sgi.com>,
Matt Mackall <mpm@selenic.com>,
blaisorblade@yahoo.it, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] slob: fix linking for user mode linux
Date: Tue, 12 Feb 2008 08:23:54 +0200 [thread overview]
Message-ID: <47B13B7A.3020003@cs.helsinki.fi> (raw)
In-Reply-To: <20080211233224.GA11432@c2.user-mode-linux.org>
Jeff Dike wrote:
>> UML defined its own external __kmalloc and things. Isnt there some other
>> way to fix it? I guess including slab.h is not possible here?
>
> It would be an annoyance to reintroduce um_kmalloc, but that might be
> the best thing to do here.
I'm ok with that as long as we get this annoying bug fixed.
prev parent reply other threads:[~2008-02-12 6:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 22:32 [PATCH] slob: fix linking for user mode linux Pekka J Enberg
2008-02-11 22:39 ` Matt Mackall
2008-02-11 22:44 ` Christoph Lameter
2008-02-11 23:32 ` Jeff Dike
2008-02-12 6:23 ` Pekka Enberg [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=47B13B7A.3020003@cs.helsinki.fi \
--to=penberg@cs.helsinki.fi \
--cc=blaisorblade@yahoo.it \
--cc=clameter@sgi.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
/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