linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Jerry Van Baren <gvb.uboot@gmail.com>
Cc: linuxppc-dev@ozlabs.org, jdl@jdl.com
Subject: Re: [PATCH dtc] Add -o <output file> to the usage message.
Date: Sun, 15 Apr 2007 10:44:55 +1000	[thread overview]
Message-ID: <20070415004455.GF9104@localhost.localdomain> (raw)
In-Reply-To: <20070414221647.GB23870@dellserver.lan>

On Sat, Apr 14, 2007 at 06:16:47PM -0400, Jerry Van Baren wrote:
> 
> Signed-off-by: Gerald Van Baren <vanbaren@cideas.com>

Acked-by: David Gibson <david@gibson.dropbear.id.au>

> ---
> 
> Hi Jon,
> 
> It turns out -o <file> was there all along, just not in the usage. :-)

Oops..

> (Jon: sorry for the dup, I messed up the linuxppc-dev@ozlabs.org address
> the first time).
> 
> Best regards,
> gvb
> 
> 
>  dtc.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/dtc.c b/dtc.c
> index a94a402..5767834 100644
> --- a/dtc.c
> +++ b/dtc.c
> @@ -83,6 +83,7 @@ static void usage(void)
>  	fprintf(stderr, "\t\t\tdts - device tree source text\n");
>  	fprintf(stderr, "\t\t\tdtb - device tree blob\n");
>  	fprintf(stderr, "\t\t\tfs - /proc/device-tree style directory\n");
> +	fprintf(stderr, "\t-o <output file>\n");
>  	fprintf(stderr, "\t-O <output format>\n");
>  	fprintf(stderr, "\t\tOutput formats are:\n");
>  	fprintf(stderr, "\t\t\tdts - device tree source text\n");

-- 
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

  reply	other threads:[~2007-04-15  0:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-14 22:16 [PATCH dtc] Add -o <output file> to the usage message Jerry Van Baren
2007-04-15  0:44 ` David Gibson [this message]
2007-04-19 22:28 ` 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=20070415004455.GF9104@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=gvb.uboot@gmail.com \
    --cc=jdl@jdl.com \
    --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).