linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 13 Mar 2007 19:00:55 +0100	[thread overview]
Message-ID: <1173808855.24454.80.camel@localhost.localdomain> (raw)
In-Reply-To: <OF526C2D02.381593EB-ON8725729D.005FC841-8525729D.0060FE86@us.ibm.com>


> I understand - I guess I am just thinking of the case where someone didn't 
> define the property because they were not aware of it - esp in this case 
> where the existence of the property name is all that is required for the 
> value to be filled in properly by the init code.  Instead of just setting 
> the start/end to 0 - maybe include a message something like (even if 
> debug) "No initird-start/end property found - setting to 0" - just a minor 
> example.  The larger point also being that defining dts files and 
> properties may be a new thing for many people with the new support - might 
> be helpful to surface missing properties when appropriate (I'm not 
> condoning mass amounts of messages for everything). 

I think the proper thing to do instead is improve the documentation :-)

Ben.

  reply	other threads:[~2007-03-13 18:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-13 17:43 Fw: [PATCH 2/15] Automatically lmb_reserve() initrd Stephen Winiecki
2007-03-13 18:00 ` Benjamin Herrenschmidt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-03-12 20:21 Stephen Winiecki
2007-03-12 21:25 ` 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=1173808855.24454.80.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).