From: Segher Boessenkool <segher@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: john stultz <johnstul@us.ibm.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
David Woodhouse <dwmw2@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linuxppc-dev@ozlabs.org
Subject: Re: Make sure we populate the initroot filesystem late enough
Date: Mon, 26 Feb 2007 17:00:49 +0100 [thread overview]
Message-ID: <f42ffce99aed41ad91cb96c10e67d908@kernel.crashing.org> (raw)
In-Reply-To: <1172505207.11949.15.camel@localhost.localdomain>
> And check that we didn't end up stupidly having the initrd share a page
> with something else ... (like not aligned end or such thingy).
David tested that yesterday, it's not the case. Too bad,
would have been too easy ;-)
Segher
WARNING: multiple messages have this Message-ID (diff)
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
john stultz <johnstul@us.ibm.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linuxppc-dev@ozlabs.org
Subject: Re: Make sure we populate the initroot filesystem late enough
Date: Mon, 26 Feb 2007 17:00:49 +0100 [thread overview]
Message-ID: <f42ffce99aed41ad91cb96c10e67d908@kernel.crashing.org> (raw)
In-Reply-To: <1172505207.11949.15.camel@localhost.localdomain>
> And check that we didn't end up stupidly having the initrd share a page
> with something else ... (like not aligned end or such thingy).
David tested that yesterday, it's not the case. Too bad,
would have been too easy ;-)
Segher
next prev parent reply other threads:[~2007-02-26 16:00 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200612112059.kBBKx1j7022473@hera.kernel.org>
2007-02-26 0:00 ` Make sure we populate the initroot filesystem late enough David Woodhouse
2007-02-26 0:00 ` David Woodhouse
2007-02-26 0:24 ` Linus Torvalds
2007-02-26 0:24 ` Linus Torvalds
2007-02-26 0:45 ` David Woodhouse
2007-02-26 0:45 ` David Woodhouse
2007-02-26 1:17 ` David Woodhouse
2007-02-26 1:17 ` David Woodhouse
2007-02-26 3:45 ` Linus Torvalds
2007-02-26 3:45 ` Linus Torvalds
2007-02-26 4:01 ` David Woodhouse
2007-02-26 4:01 ` David Woodhouse
2007-02-26 4:13 ` Linus Torvalds
2007-02-26 4:13 ` Linus Torvalds
2007-02-26 16:24 ` David Woodhouse
2007-02-26 16:24 ` David Woodhouse
2007-02-26 6:59 ` William Lee Irwin III
2007-02-26 6:59 ` William Lee Irwin III
2007-02-26 15:53 ` Benjamin Herrenschmidt
2007-02-26 15:53 ` Benjamin Herrenschmidt
2007-02-26 16:00 ` Segher Boessenkool [this message]
2007-02-26 16:00 ` Segher Boessenkool
2007-02-26 16:44 ` Milton Miller
2007-02-26 16:44 ` Milton Miller
2007-02-26 20:57 ` David Woodhouse
2007-02-26 20:57 ` David Woodhouse
2007-02-26 21:17 ` Linus Torvalds
2007-02-26 21:17 ` Linus Torvalds
2007-02-27 6:46 ` Benjamin Herrenschmidt
2007-02-27 6:46 ` Benjamin Herrenschmidt
2007-02-26 15:51 ` Benjamin Herrenschmidt
2007-02-26 15:51 ` Benjamin Herrenschmidt
2007-02-26 20:51 ` Kumar Gala
2007-02-26 20:51 ` Kumar Gala
2007-02-26 19:27 ` john stultz
2007-02-26 19:27 ` john stultz
2007-02-26 22:27 ` Paul TBBle Hampson
2007-02-26 22:27 ` Paul TBBle Hampson
2007-02-27 6:48 ` Benjamin Herrenschmidt
2007-02-27 6:48 ` Benjamin Herrenschmidt
2007-02-27 11:58 ` Segher Boessenkool
2007-02-27 11:58 ` Segher Boessenkool
2007-02-28 6:43 ` Benjamin Herrenschmidt
2007-02-28 6:43 ` Benjamin Herrenschmidt
2007-02-28 10:13 ` David Woodhouse
2007-02-28 10:13 ` David Woodhouse
2007-03-01 0:30 ` Michael Ellerman
2007-03-01 0:30 ` Michael Ellerman
2007-03-12 23:01 ` Paul TBBle Hampson
2007-03-12 23:01 ` Paul TBBle Hampson
2007-03-13 3:03 ` Kumar Gala
2007-03-13 3:03 ` Kumar Gala
2007-03-13 7:03 ` Benjamin Herrenschmidt
2007-03-13 7:03 ` Benjamin Herrenschmidt
2007-03-16 7:20 ` Paul TBBle Hampson
2007-03-16 7:20 ` Paul TBBle Hampson
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=f42ffce99aed41ad91cb96c10e67d908@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=benh@kernel.crashing.org \
--cc=dwmw2@infradead.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--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 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.