From: Denys Vlasenko <vda.linux@googlemail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
Andi Kleen <andi@firstfloor.org>,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
Paul Gortmaker <paul.gortmaker@windriver.com>,
linux-embedded@vger.kernel.org, linux-kernel@vger.kernel.org,
Tim Bird <tim.bird@am.sony.com>
Subject: Re: [PATCH 0/1] Embedded Maintainer(s), linux-embedded@vger list
Date: Mon, 23 Jun 2008 21:12:30 +0200 [thread overview]
Message-ID: <200806232112.30393.vda.linux@googlemail.com> (raw)
In-Reply-To: <20080623185728.GB30550@uranus.ravnborg.org>
On Monday 23 June 2008 20:57, Sam Ravnborg wrote:
> > > I agree. And if we do want to pay attention to pure code size, there are
> > > other approaches -- like --gc-sections
> >
> > I have some patches in this area too. Were submitted to Sam
> > but he was too busy it seems.
>
> They were not trivial to apply and so went down on the TODO list.
I realize that they were not trivial to review, but that
was unavoidable. They were even more not trivial to create.
> We could try to push the generic and x86 specific .lds stuff via
> the arch maintainers?
IIRC I splitted the entire GC collection patch in a way
that first patches were doing exactly this easier first part
and I hoped that at least these first patches
will be taken. They were big, but somewhat trivial,
from "it's obviously safe" department.
Had they been applied, now making --gc-sections to work
would be easier.
--
vda
next prev parent reply other threads:[~2008-06-23 19:12 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 17:42 [PATCH 0/1] Embedded Maintainer(s), linux-embedded@vger list David Woodhouse
2008-04-30 17:44 ` [PATCH 1/1] " David Woodhouse
2008-05-01 9:55 ` Bart Van Assche
2008-05-01 10:05 ` David Woodhouse
2008-05-01 11:12 ` Bart Van Assche
2008-04-30 18:22 ` [PATCH 0/1] " Andi Kleen
2008-04-30 19:11 ` David Woodhouse
2008-06-23 17:22 ` Denys Vlasenko
2008-06-23 18:57 ` Sam Ravnborg
2008-06-23 19:12 ` Denys Vlasenko [this message]
2008-06-23 19:33 ` Sam Ravnborg
[not found] ` <48190B5F.9010505@am.sony.com>
[not found] ` <20080501095822.GL20451@one.firstfloor.org>
2008-05-01 10:02 ` David Woodhouse
2008-05-01 10:41 ` Andi Kleen
2008-05-02 15:00 ` Pekka Enberg
2008-05-02 20:01 ` Eduard - Gabriel Munteanu
2008-05-02 20:14 ` Andrew Morton
2008-05-02 20:33 ` Eduard - Gabriel Munteanu
2008-05-02 20:53 ` Andrew Morton
2008-05-03 22:24 ` Randy Dunlap
2008-05-05 1:52 ` Andrew Morton
2008-06-23 17:28 ` Denys Vlasenko
2008-06-23 17:45 ` Adrian Bunk
2008-06-23 18:19 ` Denys Vlasenko
2008-06-23 19:05 ` Tim Bird
2008-06-25 9:50 ` James Chapman
2008-06-25 15:41 ` Adrian Bunk
2008-04-30 18:26 ` Josh Boyer
2008-04-30 18:43 ` David Woodhouse
2008-04-30 18:45 ` Josh Boyer
2008-04-30 23:34 ` Adrian Bunk
2008-05-01 7:04 ` David Woodhouse
2008-05-02 11:58 ` Kristoffer Ericson
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=200806232112.30393.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=dwmw2@infradead.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=sam@ravnborg.org \
--cc=tim.bird@am.sony.com \
--cc=torvalds@linux-foundation.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