All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, 2/6] fdt: Limit printed hex in fdt print and list commands
Date: Sun, 28 Oct 2012 20:54:52 -0400	[thread overview]
Message-ID: <508DD3DC.3030608@gmail.com> (raw)
In-Reply-To: <20121025205955.GA6338@bill-the-cat>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Tom, Joe,

On 10/25/2012 04:59 PM, Tom Rini wrote:
> On Fri, Aug 17, 2012 at 10:34:36AM -0000, Joe Hershberger wrote:
> 
>> Prevent printing the entire image in a itb. It is most likely 
>> unhelpful to have the hex of the entire image scroll for minutes 
>> on your slow serial console.
>> 
>> Signed-off-by: Joe Hershberger <joe.hershberger@ni.com>
> 
> This causes: $ uboot-build.sh sandboxTesting sandbox on 
> -00004-gf0a29d4 Thu Oct 25 13:59:03 MST 2012 Configuring for 
> sandbox board... text    data     bss     dec     hex filename 
> 140245    6332   28472  175049   2abc9 sandbox/u-boot cmd_fdt.c:
> In function 'print_data': cmd_fdt.c:679:32: warning: cast from
> pointer to integer of different size [-Wpointer-to-int-cast] 
> cmd_fdt.c:691:32: warning: cast from pointer to integer of 
> different size [-Wpointer-to-int-cast]

Sorry, I should have caught that and the 3/6 warning. :-(

I'm tied up with a flight test through Friday (Nov 2) which has been
consuming all my available time.  Joe, can you look at fixing the
warnings?

Thanks,
gvb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQEcBAEBAgAGBQJQjdPPAAoJEGOcKeGailWqeSMH/itjpDTCi/dNf3wdDHImpTev
r9A7Ygk01eLhPWlLX5sV9+GziO1x1s8Z9mRbpdIBz4NeA5vaB79wS3D2/S06dxh8
DeSlk3U8eo4tNiI9OysDDp5IyxNXEmje4KkOD8snLIeYKV3/1RDPQYzsLrzlGVJ6
dFjPGNHmjLWzMi4kOSR34b6SIl1xPCUtBUgMfMTN6R8S5JLuJKSn/WUUcXtHpras
yKYfvs1ULkmMg4aEbKzCWFa/a/JJK+XlxU4XQX2Xd7HSISg0eIoOJSV5khTCG8gR
SVCkbF89+XO749a9xL3jyTEz1xMPqFO3KugbnyZGtsOm87VWyuZ/qzR4KdC2rJA=
=ox6g
-----END PGP SIGNATURE-----

  reply	other threads:[~2012-10-29  0:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17 20:34 [U-Boot] [PATCH 1/6] fdt: Check error codes returned from fdtlib when loading ITB Joe Hershberger
2012-08-17 20:34 ` [U-Boot] [PATCH 2/6] fdt: Limit printed hex in fdt print and list commands Joe Hershberger
2012-10-25 20:59   ` [U-Boot] [U-Boot, " Tom Rini
2012-10-29  0:54     ` Jerry Van Baren [this message]
2012-08-17 20:34 ` [U-Boot] [PATCH 3/6] fdt: Add get commands to fdt Joe Hershberger
2012-10-25 21:08   ` [U-Boot] [U-Boot,3/6] " Tom Rini
2012-08-17 20:34 ` [U-Boot] [PATCH 4/6] fdt: Identify scripts in ITBs as printable strings Joe Hershberger
2012-08-17 20:34 ` [U-Boot] [PATCH 5/6] fdt: Check for a token to skip auto-hash validation Joe Hershberger
2012-08-17 20:34 ` [U-Boot] [PATCH 6/6] fdt: Add a Linux tool for reading values from FDT files Joe Hershberger
2012-08-17 23:35   ` Mike Frysinger
2012-08-20 23:40     ` Joe Hershberger
2012-08-21  0:24       ` Mike Frysinger
2012-08-21  0:51         ` Joe Hershberger
2012-08-21  3:51           ` Mike Frysinger
2012-09-23 23:06             ` Marek Vasut
2012-10-04 17:38 ` [U-Boot] [PATCH 1/6] fdt: Check error codes returned from fdtlib when loading ITB Joe Hershberger
2012-10-08 23:45   ` Jerry Van Baren
2012-10-08 23:51     ` Tom Rini

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=508DD3DC.3030608@gmail.com \
    --to=gvb.uboot@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.