public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@jdl•com>
To: David Gibson <david@gibson•dropbear.id.au>
Cc: "linuxppc-dev@ozlabs•org" <linuxppc-dev@ozlabs•org>
Subject: Re: Outstanding DTC patches?
Date: Thu, 03 Jan 2008 08:14:53 -0600	[thread overview]
Message-ID: <E1JAQqT-00056B-FP@jdl.com> (raw)
In-Reply-To: Your message of "Thu, 03 Jan 2008 15:48:43 +1100." <20080103044843.GD25357@localhost.localdomain>

So, like, the other day David Gibson mumbled:
> 
> I posted this one a while back, but I guess it dropped through the
> cracks.

Yep, sorry.

> There's also the patch I sent you quite a long time ago that
> adds a clarifying readme about the licensing situation - that might be
> an idea for v1.1, too.

I can not find this; neither locally nor on patchworks.
Do you have a Subject: line, a URL, or could you
please repost it?


> dtc: Remove header information dumping
> 
> Currently, when used in -Idtb mode, dtc will dump information about
> the input blob's header fields to stderr.  This is kind of ugly, and
> can get in the way of dtc's real output.
> 
> This patch, therefore, removes this.  So that there's still a way of
> getting this information for debugging purposes, it places something
> similar to the removed code into ftdump, replacing the couple of
> header fields it currently prints with a complete header dump.
> 
> Signed-off-by: David Gibson <david@gibson•dropbear.id.au>

Applied.

Thanks,
jdl

  reply	other threads:[~2008-01-03 14:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-02 18:21 Outstanding DTC patches? Jon Loeliger
2008-01-03  4:48 ` David Gibson
2008-01-03 14:14   ` Jon Loeliger [this message]
2008-01-04  2:43     ` David Gibson
2008-01-04 14:38       ` 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=E1JAQqT-00056B-FP@jdl.com \
    --to=jdl@jdl$(echo .)com \
    --cc=david@gibson$(echo .)dropbear.id.au \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /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