From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Meelis Roos <mroos@linux.ee>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Richard Henderson <rth@twiddle.net>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Jay Estabrook <jay.estabrook@hp.com>
Subject: Re: [PATCH] lib: move kasprintf to a separate file
Date: Sat, 28 Jul 2007 15:48:32 -0700 [thread overview]
Message-ID: <46ABC7C0.9060302@goop.org> (raw)
In-Reply-To: <20070728202012.GB25619@uranus.ravnborg.org>
Sam Ravnborg wrote:
> kasprintf pulls in kmalloc which proved to be fatal for at least
> bootimage target on alpha.
> Move it to a separate file so only users of kasprintf are exposed
> to the dependency on kmalloc.
>
OK by me (that's what my original patch did), but it might be worth
documenting what environmental constraints vsprintf.c is under. I
didn't realize it was used by non-kernel code.
J
next prev parent reply other threads:[~2007-07-28 22:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 11:21 alpha compile failure (srm_printk) Meelis Roos
2007-06-06 6:17 ` Andrew Morton
2007-06-06 7:48 ` Meelis Roos
2007-07-28 17:05 ` Meelis Roos
2007-07-28 20:04 ` Sam Ravnborg
2007-07-28 20:20 ` [PATCH] lib: move kasprintf to a separate file Sam Ravnborg
2007-07-28 20:52 ` [PATCH] add a missing LIB_Y to arch/alpha/boot Makefile Meelis Roos
2007-07-28 22:48 ` Jeremy Fitzhardinge [this message]
2007-07-29 20:08 ` [PATCH] lib: move kasprintf to a separate file Sam Ravnborg
2007-07-28 20:21 ` alpha compile failure (srm_printk) Sam Ravnborg
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=46ABC7C0.9060302@goop.org \
--to=jeremy@goop.org \
--cc=akpm@linux-foundation.org \
--cc=ink@jurassic.park.msu.ru \
--cc=jay.estabrook@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=rth@twiddle.net \
--cc=sam@ravnborg.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