linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: Fix whitespace merge in mpc8641 hpcn device tree
Date: Thu, 31 Jul 2008 17:52:11 -0500	[thread overview]
Message-ID: <4892421B.3020704@freescale.com> (raw)
In-Reply-To: <BF7C9A64-AABC-4624-8282-4BAC2D970009@kernel.crashing.org>

Kumar Gala wrote:
> np.  It would be nice to see dtc warn about it, but that would probably 
> be a bit difficult.

One thing that macros may bring besides clarity and elimination of 
redundancy is the ability to put some semantic checks in the macro 
itself (rather than hardcoding it into dtc).  At the very least, this 
particular bug would show up as the wrong number of arguments to a macro.

-Scott

  reply	other threads:[~2008-07-31 22:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31 22:10 [PATCH] powerpc: Fix whitespace merge in mpc8641 hpcn device tree Kumar Gala
2008-07-31 22:18 ` Jon Loeliger
2008-07-31 22:28   ` Kumar Gala
2008-07-31 22:52     ` Scott Wood [this message]
2008-08-01  3:20     ` David Gibson

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=4892421B.3020704@freescale.com \
    --to=scottwood@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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).