From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stephen Winiecki <stevewin@us.ibm.com>
Cc: linuxppc-dev@ozlabs.org, david@gibson.dropbear.id.au
Subject: Re: Fw: [PATCH 2/15] Automatically lmb_reserve() initrd
Date: Mon, 12 Mar 2007 22:25:32 +0100 [thread overview]
Message-ID: <1173734732.24454.52.camel@localhost.localdomain> (raw)
In-Reply-To: <OF0BE55B3C.650D62FC-ON8725729C.006DDB97-8525729C.006F8642@us.ibm.com>
> It might be helpful if some kind of message was surfaced if the
> initrd-start/end properties didn't exist in the dt, esp. since it may not
> be well known initially as a dts definition requirement/option (voice of
> experience :)). In general I think surfacing messages for any properties
> which are detected as not existing and which might be normally expected
> would be a good thing as people get familiar with defining dts files and
> specifying properties for their platforms.
Well.. initrd is totally optional...
Ben.
next prev parent reply other threads:[~2007-03-12 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 20:21 Fw: [PATCH 2/15] Automatically lmb_reserve() initrd Stephen Winiecki
2007-03-12 21:25 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-13 17:43 Stephen Winiecki
2007-03-13 18:00 ` Benjamin Herrenschmidt
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=1173734732.24454.52.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=stevewin@us.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).