linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@jdl.com>
To: Michael Neuling <mikey@neuling.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] dtc: add setting of physical boot cpu
Date: Wed, 07 Jun 2006 09:49:43 -0500	[thread overview]
Message-ID: <E1FnzLr-0007Ot-NL@jdl.com> (raw)
In-Reply-To: Your message of "Wed, 31 May 2006 08:31:51 +1000." <20060530223309.9AB7667B3E@ozlabs.org>

So, like, the other day Michael Neuling mumbled:
> dtc always sets the physical boot CPU to 0xfeedbeef.  Add a -b option to
> set this.    Also add warnings when using the wrong property with the
> wrong blob version.  
> 
> Signed-off-by: Michael Neuling <mikey@neuling.org>

Applied and pushed out to:

     http://www.jdl.com/git_repos

Sorry for the hang time.

Thanks,
jdl

      reply	other threads:[~2006-06-07 15:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-18  3:56 [PATCH] dtc: add setting of physical boot cpu Michael Neuling
2006-05-18 13:23 ` Jimi Xenidis
2006-05-18 16:59   ` Michael Neuling
2006-05-30 22:31     ` Michael Neuling
2006-06-07 14:49       ` Jon Loeliger [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=E1FnzLr-0007Ot-NL@jdl.com \
    --to=jdl@jdl.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mikey@neuling.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 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).