From: Ingo Molnar <mingo@elte.hu>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, Simon Arlott <simon@fire.lp0.eu>,
Daniel Walker <dwalker@mvista.com>,
Rene Herman <rene.herman@keyaccess.nl>
Subject: Re: [patch 0/4] Second batch of fastboot patches: get rid of the 2 second rootfs delay
Date: Mon, 21 Jul 2008 17:52:49 +0200 [thread overview]
Message-ID: <20080721155249.GA9607@elte.hu> (raw)
In-Reply-To: <20080720151436.26bdc717@infradead.org>
* Arjan van de Ven <arjan@infradead.org> wrote:
> Hi,
>
> this second batch of fastboot patches gets rid of the delay you can
> get when you're not using an initrd; on my system this delay is a full
> 2 seconds (which is longer than the whole kernel boot combined).
>
> I've also stuck the patch series into a git tree
>
> clone git://git.kernel.org/pub/scm/linux/git/arjan/linux-2.6-fastboot
thanks, pulled into tip/fastboot - works great here!
Ingo
prev parent reply other threads:[~2008-07-21 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 22:14 [patch 0/4] Second batch of fastboot patches: get rid of the 2 second rootfs delay Arjan van de Ven
2008-07-21 1:46 ` Daniel Walker
2008-07-21 8:01 ` Rene Herman
2008-07-21 15:52 ` Ingo Molnar [this message]
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=20080721155249.GA9607@elte.hu \
--to=mingo@elte.hu \
--cc=arjan@infradead.org \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.herman@keyaccess.nl \
--cc=simon@fire.lp0.eu \
/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