linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@jdl.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-dev@ozlabs.org, 5B@ozlabs.org
Subject: Re: dtc: Remove bogus break statement
Date: Mon, 02 Jul 2007 08:33:44 -0500	[thread overview]
Message-ID: <E1I5M2C-0005bM-M9@jdl.com> (raw)
In-Reply-To: Your message of "Thu, 28 Jun 2007 11:32:31 +1000." <20070628013231.GF15298@localhost.localdomain>

So, like, the other day David Gibson mumbled:
> Commit 0738774fcc34b78a708a127fb4b2f193d08c94ba introduced some
> incorrect indentation / bracketing in unflatten_tree().  By luck, the
> extra break statement intended to be within an if block, but actually
> afterwards has no semantic effect.  Still, this patch gets rid of it
> for cleanliness.
> 
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>

Applied.

Thanks,
jdl

      reply	other threads:[~2007-07-02 13:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-28  1:32 dtc: Remove bogus break statement David Gibson
2007-07-02 13:33 ` 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=E1I5M2C-0005bM-M9@jdl.com \
    --to=jdl@jdl.com \
    --cc=5B@ozlabs.org \
    --cc=david@gibson.dropbear.id.au \
    --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).