All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: linux-mips@linux-mips.org
Subject: Re: [PATCH]: Rewrite of arch/mips/ramdisk/
Date: Mon, 15 Nov 2004 20:21:34 -0500	[thread overview]
Message-ID: <4199561E.9040500@gentoo.org> (raw)
In-Reply-To: <20041115175514.GA6069@linux-mips.org>

Ralf Baechle wrote:
> 
> I guess you and many others don't realize the speed of the Linux evolution
> these days.  Between 2.6.10-rc1 and 2.6.10-rc2 there's about 9MB of
> patches.  Even if much of the code is not changing - the halftime for
> patches has reduced quite a bit ...

I'm aware of the speed at which the kernel changes.  What I didn't expect was 
that I picked the one time to try and fix mips embedded ramdisks with a more 
permanent fix at the same time someone else did -- just the someone else had a 
much better idea that applied more globally.  Call it bad timing with a little 
bit of coincidence mixed in.

I'll have to figure out how this CONFIG_INITRAMFS_SOURCE works now (it doesn't 
look like the Kconfig bits are in yet, a quick grep only shows mentions in 
defconfigs), and then see how it can replace the older embedded ramdisk idea.


--Kumba

-- 
"Such is oft the course of deeds that move the wheels of the world: small 
hands do them because they must, while the eyes of the great are elsewhere." 
--Elrond

  reply	other threads:[~2004-11-16  1:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-14  6:43 [PATCH]: Rewrite of arch/mips/ramdisk/ Kumba
2004-11-14  8:52 ` Christoph Hellwig
2004-11-14 17:25   ` Kumba
2004-11-14 19:31     ` Kumba
2004-11-15 17:55       ` Ralf Baechle
2004-11-16  1:21         ` Kumba [this message]
2004-11-15 18:05       ` Christoph Hellwig
2004-11-17 13:17         ` Ralf Baechle

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=4199561E.9040500@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=linux-mips@linux-mips.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.