From: Olaf Hering <olh@suse.de>
To: Paul Mackerras <paulus@samba.org>
Cc: Andrew Morton <akpm@osdl.org>, Matt Mackall <mpm@selenic.com>,
linux-kernel@vger.kernel.org, trini@kernel.crashing.org
Subject: Re: [PATCH 1/2] slob: move kstrdup to lib/string.c
Date: Wed, 2 Nov 2005 14:04:35 +0100 [thread overview]
Message-ID: <20051102130435.GA24230@suse.de> (raw)
In-Reply-To: <17256.33817.263105.197325@cargo.ozlabs.ibm.com>
On Wed, Nov 02, Paul Mackeras wrote:
> Andrew Morton writes:
>
> > > That doesn't sound kosher, have a pointer?
> > >
> >
> > http://lkml.org/lkml/2005/4/8/128
>
> Yes, we currently use bits of lib/ in the zImage boot wrapper. I
> suspect we used to have our own string routines for the boot wrapper
> until somebody said "why do we have all this code duplicated" and
> cleaned it up. :)
We cant continue to use files from lib/ in arch/powerpc/boot when they
start to use kernel internals like kmalloc. I converted a few
zlib_inflate files with sed already. But things will get really ugly if
we have to do more on-the-fly modifications. After all,
arch/$ARCH/boot is no kernel code, it has to be standalone.
Maybe we should just have no arch/powerpc/boot.
--
short story of a lazy sysadmin:
alias appserv=wotan
next prev parent reply other threads:[~2005-11-02 13:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 18:33 [PATCH 1/2] slob: move kstrdup to lib/string.c Matt Mackall
2005-11-01 18:33 ` [PATCH 2/2] slob: introduce the SLOB allocator Matt Mackall
2005-11-01 20:51 ` Rob Landley
2005-11-01 21:06 ` Matt Mackall
2005-11-02 6:00 ` [PATCH 1/2] slob: move kstrdup to lib/string.c Andrew Morton
2005-11-02 7:03 ` Matt Mackall
2005-11-02 6:40 ` Andrew Morton
2005-11-02 9:17 ` Paul Mackerras
2005-11-02 13:04 ` Olaf Hering [this message]
2005-11-02 14:14 ` Tom Rini
2005-11-02 14:19 ` Olaf Hering
2005-11-02 14:31 ` 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=20051102130435.GA24230@suse.de \
--to=olh@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=paulus@samba.org \
--cc=trini@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.