From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace•com>
To: Scott Wood <scottwood@freescale•com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: [PATCH] Remove bogus errors from check_chosen.
Date: Fri, 23 Mar 2007 11:21:27 -0400 [thread overview]
Message-ID: <4603F077.9090905@smiths-aerospace.com> (raw)
In-Reply-To: <20070323150517.GB6060@ld0162-tx32.am.freescale.net>
Scott Wood wrote:
> On Fri, Mar 23, 2007 at 02:31:58PM +1100, David Gibson wrote:
>> I'm not 100% comfortable with this patch; I'd like for dtc to have the
>> facility to do more-or-less complete tree validation.
>
> That'd be nice as long as it's optional; it should be possible to do a
> low level dts->dtb transformation without the tool assuming that the
> output is intended to be a final, valid tree with the specific bindings
> that dtc knowns about (or even an OF-ish tree at all).
>
> -Scott
It needs a -Wall ;-)
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.
gvb
next prev parent reply other threads:[~2007-03-23 15:21 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 [this message]
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
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=4603F077.9090905@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=scottwood@freescale$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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