public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: WANG Cong <xiyou.wangcong@gmail.com>
To: Jeff Dike <jdike@addtoit.com>
Cc: stable@kernel.org, LKML <linux-kernel@vger.kernel.org>,
	uml-devel <user-mode-linux-devel@lists.sourceforge.net>,
	WANG Cong <xiyou.wangcong@gmail.com>
Subject: Re: [PATCH 1/14] uml: fix build when SLOB is enabled
Date: Tue, 5 Aug 2008 10:05:02 +0100	[thread overview]
Message-ID: <20080805090502.GA3039@hack.voiplan.pt> (raw)
In-Reply-To: <20080801224125.GA13727@c2.user-mode-linux.org>

On Fri, Aug 01, 2008 at 06:41:25PM -0400, Jeff Dike wrote:
>From 94409ded7768e15b0d0a5a172d611073c72308de Mon Sep 17 00:00:00 2001
>
>Reintroduce uml_kmalloc for the benefit of UML libc code.  The
>previous tactic of declaring __kmalloc so it could be called directly
>from the libc side of the house turned out to be getting too intimate
>with slab, and it doesn't work with slob.
>
>So, the uml_kmalloc wrapper is back.  It calls kmalloc or whatever
>that translates into, and libc code calls it.
>
>kfree is left alone since that still works, leaving a somewhat
>inconsistent API.
>
>Signed-off-by: Jeff Dike <jdike@linux.intel.com>
>Cc: WANG Cong <xiyou.wangcong@gmail.com>
>Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

Looks good. Thanks. :)


-- 
The opposite of love is not hate, but indifference.
	--Elie Wiesel

  parent reply	other threads:[~2008-08-05  9:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01 22:41 [PATCH 1/14] uml: fix build when SLOB is enabled Jeff Dike
2008-08-01 23:06 ` [stable] " Greg KH
2008-08-02  1:00   ` Jeff Dike
2008-08-05  9:05 ` WANG Cong [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-08-05 20:14 Jeff Dike

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=20080805090502.GA3039@hack.voiplan.pt \
    --to=xiyou.wangcong@gmail.com \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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