From: David Gibson <david@gibson.dropbear.id.au>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [DTC PATCH] Remove overreaching semantic tests.
Date: Tue, 15 May 2007 10:57:28 +1000 [thread overview]
Message-ID: <20070515005728.GA565@localhost.localdomain> (raw)
In-Reply-To: <46488597.5060109@freescale.com>
On Mon, May 14, 2007 at 10:51:51AM -0500, Scott Wood wrote:
> David Gibson wrote:
> > On Fri, May 11, 2007 at 12:55:54PM -0500, Scott Wood wrote:
> >>I wouldn't be opposed to keeping these tests around if there were a
> >>command line option that cleanly separates the errors/warnings into
> >>classes such as structural, semantic-missing, semantic-broken, etc.
> >
> > Exactly - which is why I really don't want to simply tear out this
> > checking code. I've never gotten around to reworking the
> > error/warning system so it can sensibly divide things into such
> > classes, and keep detecting further warnings after picking up some
> > non-fatal ones and so forth.
> >
> > I'd much prefer you just disable these tests for now, either by
> > commenting code out, or removing calls to checking functions. That
> > will make it easier to optionally reinstate later.
>
> Well, I figured the code would still be there in git, so getting it back
> wouldn't be too hard. I can submit a patch that hides it behind a
> --warn-missing (or whatever) option, though.
I'd prefer that, thank you.
--
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
prev parent reply other threads:[~2007-05-15 0:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 17:55 [DTC PATCH] Remove overreaching semantic tests Scott Wood
2007-05-14 1:19 ` David Gibson
2007-05-14 12:40 ` Segher Boessenkool
2007-05-14 15:51 ` Scott Wood
2007-05-15 0:57 ` David Gibson [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=20070515005728.GA565@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 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).