From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org,
Christian.Limpach@cl.cam.ac.uk, chrisw@sous-sol.org
Subject: Re: [PATCH] Implement kasprintf
Date: Tue, 20 Jun 2006 17:14:55 -0700 [thread overview]
Message-ID: <44988F7F.2010502@goop.org> (raw)
In-Reply-To: <20060620171020.301add23.rdunlap@xenotime.net>
Randy.Dunlap wrote:
> Why do we want a separate source file for this one function?
>
Because if it shared a file with something else, someone would complain
about it bloating code which doesn't use it... At the moment there are
no in-tree users (though I'm sure there's something out there with an
open-coded version of this), but we'll be needing it for Xen.
I'm happy to fold it into vsprintf.c though.
J
next prev parent reply other threads:[~2006-06-21 0:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 23:57 [PATCH] Implement kasprintf Jeremy Fitzhardinge
2006-06-21 0:10 ` Randy.Dunlap
2006-06-21 0:14 ` Jeremy Fitzhardinge [this message]
2006-06-21 0:26 ` Randy.Dunlap
2006-06-21 0:31 ` Jeremy Fitzhardinge
2006-06-21 3:04 ` Kyle McMartin
2006-06-21 3:26 ` Andrew Morton
2006-06-21 4:30 ` H. Peter Anvin
2006-06-21 11:58 ` Kyle McMartin
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=44988F7F.2010502@goop.org \
--to=jeremy@goop.org \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.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