From: David Gibson <david@gibson.dropbear.id.au>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Remove bogus errors from check_chosen.
Date: Sat, 24 Mar 2007 10:40:32 +1100 [thread overview]
Message-ID: <20070323234032.GE4459@localhost.localdomain> (raw)
In-Reply-To: <20070323153609.GE6060@ld0162-tx32.am.freescale.net>
On Fri, Mar 23, 2007 at 10:36:09AM -0500, Scott Wood wrote:
> On Fri, Mar 23, 2007 at 11:21:27AM -0400, Jerry Van Baren wrote:
> > The -q[q[q]] I added cuts down/eliminates the moaning, but you still
> > have to -f force the output which doesn't match what Scott is advocating
> > if I understand him.
> >
> > The gcc -Wall is backwards to what we should have, perhaps adding --no*
> > options like:
> > --nochosen
> > --nocpu
> > --noarmyboots
> > to tell dtc that lonely barefoot blobs are OK.
>
> There should also be a --no-validate option to turn everything off, if
> the user is confident that the tree is right and doesn't want to get
> broken by new dtcs that have new error categories (or if the user is
> using dtc to compile some other type of tree than an OF-ish device tree).
That's what -f is.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-03-23 23:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 16:11 [PATCH] Remove bogus errors from check_chosen Scott Wood
2007-03-22 16:22 ` Scott Wood
2007-03-23 3:31 ` David Gibson
2007-03-23 15:05 ` Scott Wood
2007-03-23 15:21 ` Jerry Van Baren
2007-03-23 15:36 ` Scott Wood
2007-03-23 15:48 ` Jerry Van Baren
2007-03-23 23:42 ` David Gibson
2007-03-23 23:40 ` David Gibson [this message]
2007-03-23 16:03 ` Jon Loeliger
2007-03-23 23:51 ` David Gibson
2007-03-26 13:35 ` Jon Loeliger
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=20070323234032.GE4459@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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 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.