public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	mpm@selenic.com
Subject: Re: [PATCH] Use directly kmalloc() and kfree() in init/initramfs.c
Date: Fri, 15 Feb 2008 17:04:22 +0100	[thread overview]
Message-ID: <20080215170422.192de4df@crazy> (raw)
In-Reply-To: <Pine.LNX.4.64.0802151658320.30301@fbirervta.pbzchgretzou.qr>

[-- Attachment #1: Type: text/plain, Size: 842 bytes --]

Le Fri, 15 Feb 2008 17:00:35 +0100 (CET),
Jan Engelhardt <jengelh@computergmbh.de> a écrit :

> Anyone you can get to push the actual changeset; many won't feel
> responsible :) so the path is through ->akpm->linus here.

Ok, so as Andrew is in Cc:, I suppose he will pick the patch :-)

> BTW, if you changed free to kfree, did the free macro/whatever get 
> removed or is it still used?

After this patch, they are still used by the lib/inflate.c code. But if
you look at the patch called "inflate: refactor inflate malloc code"
that I sent to the LKML this morning, you'll see that it removes the
malloc() and free() wrappers (and does some more clean-up).

Sincerly,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Free Embedded Linux Training Materials
on http://free-electrons.com/training
(More than 1500 pages!)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2008-02-15 16:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-15 11:13 [PATCH] Use directly kmalloc() and kfree() in init/initramfs.c Thomas Petazzoni
2008-02-15 14:46 ` Jan Engelhardt
2008-02-15 15:45   ` Thomas Petazzoni
2008-02-15 16:00     ` Jan Engelhardt
2008-02-15 16:04       ` Thomas Petazzoni [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=20080215170422.192de4df@crazy \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=akpm@linux-foundation.org \
    --cc=jengelh@computergmbh.de \
    --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