From: Paulo Marques <pmarques@grupopie.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Matt Mackall <mpm@selenic.com>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] slob: introduce mm/util.c for shared functions
Date: Fri, 04 Nov 2005 15:46:57 +0000 [thread overview]
Message-ID: <436B8271.7040809@grupopie.com> (raw)
In-Reply-To: <84144f020511040020n7ae5a460ud9ba5bbec9317748@mail.gmail.com>
Pekka Enberg wrote:
> On 11/4/05, Matt Mackall <mpm@selenic.com> wrote:
>
>>Well, yes. But I decided not to do that now because I ended up wanting
>>to create mm/util.c anyway for kzalloc. I suspect we'll see other
>>helper functions like kzalloc and kstrdup down the road.
>
> I prefer this as well. kstrdup() is _not_ a string operation but a
> special purpose memory allocator just like kzalloc() and kcalloc().
It is even worse than just personal preference.
Having kstrdup in lib/string was actually tried first, but there are
archs that use lib/string for their boot code.
This boot code has no kmalloc available, so the dependency of kstrdup on
kmalloc breaks the build for them if kstrdup is moved to lib/string.
--
Paulo Marques - www.grupopie.com
The rule is perfect: in all matters of opinion our
adversaries are insane.
Mark Twain
next prev parent reply other threads:[~2005-11-04 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 23:00 [PATCH 1/2] slob: introduce mm/util.c for shared functions Matt Mackall
2005-11-03 23:00 ` [PATCH 2/2] slob: introduce the SLOB allocator Matt Mackall
2005-11-04 5:13 ` [PATCH 1/2] slob: introduce mm/util.c for shared functions Andrew Morton
2005-11-04 6:24 ` Matt Mackall
2005-11-04 8:20 ` Pekka Enberg
2005-11-04 15:46 ` Paulo Marques [this message]
2005-11-07 20:29 ` Tom Rini
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=436B8271.7040809@grupopie.com \
--to=pmarques@grupopie.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=penberg@cs.helsinki.fi \
/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