From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Jeremy Fitzhardinge <jeremy@goop.org>
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:26:00 -0700 [thread overview]
Message-ID: <20060620172600.9294cd00.rdunlap@xenotime.net> (raw)
In-Reply-To: <44988F7F.2010502@goop.org>
On Tue, 20 Jun 2006 17:14:55 -0700 Jeremy Fitzhardinge wrote:
> 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.
Doesn't this already add the bloat/code? ::
diff -r c175fd50e604 lib/Makefile
--- a/lib/Makefile Tue Jun 20 16:47:53 2006 -0700
+++ b/lib/Makefile Tue Jun 20 16:53:19 2006 -0700
@@ -5,7 +5,7 @@ lib-y := errno.o ctype.o string.o vsprin
lib-y := errno.o ctype.o string.o vsprintf.o cmdline.o \
bust_spinlocks.o rbtree.o radix-tree.o dump_stack.o \
idr.o div64.o int_sqrt.o bitmap.o extable.o prio_tree.o \
- sha1.o
+ sha1.o kasprintf.o
> I'm happy to fold it into vsprintf.c though.
That makes sense to me.
Thanks,
---
~Randy
next prev parent reply other threads:[~2006-06-21 0:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 23:57 Jeremy Fitzhardinge
2006-06-21 0:10 ` Randy.Dunlap
2006-06-21 0:14 ` Jeremy Fitzhardinge
2006-06-21 0:26 ` Randy.Dunlap [this message]
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=20060620172600.9294cd00.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®