From: David Gibson <david@gibson.dropbear.id.au>
To: Milton Miller <miltonm@bga.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/4] powerpc: Add gcc format warnings to zImage printf()
Date: Thu, 22 Mar 2007 12:35:01 +1100 [thread overview]
Message-ID: <20070322013501.GG2295@localhost.localdomain> (raw)
In-Reply-To: <200703211503.l2LF3JRS008531@sullivan.realtime.net>
On Wed, Mar 21, 2007 at 09:03:19AM -0600, Milton Miller wrote:
>
> +extern int sprintf(char *buf, const char *fmt, ...) __attribute__((format(printf, 2, 3)));
>
> you exceeded 80 columns by 10.
Revised in second spin.
--
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
next prev parent reply other threads:[~2007-03-22 1:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 6:30 [0/4] Further zImage work David Gibson
2007-03-21 6:31 ` [PATCH 2/4] powerpc: Add device tree utility functions to zImage David Gibson
2007-03-21 15:03 ` Milton Miller
2007-03-22 3:02 ` David Gibson
2007-03-21 17:10 ` Segher Boessenkool
2007-03-21 23:31 ` David Gibson
2007-03-21 21:57 ` Scott Wood
2007-03-22 1:36 ` David Gibson
2007-03-21 6:31 ` [PATCH 1/4] powerpc: Add gcc format warnings to zImage printf() David Gibson
2007-03-21 15:03 ` Milton Miller
2007-03-22 1:35 ` David Gibson [this message]
2007-03-21 6:31 ` [PATCH 4/4] powerpc: New reg.h for the zImage David Gibson
2007-03-21 6:31 ` [PATCH 3/4] powerpc: Clean up zImage handling of the command line David Gibson
2007-03-22 5:48 ` [0/4] Further zImage work (spin 2) David Gibson
2007-03-22 5:59 ` [PATCH 1/4] powerpc: Add gcc format warnings to zImage printf() David Gibson
2007-03-22 6:02 ` [PATCH 2/4] powerpc: Add device tree utility functions to zImage David Gibson
2007-03-22 6:02 ` [PATCH 4/4] powerpc: New reg.h for the zImage David Gibson
2007-03-22 6:02 ` [PATCH 3/4] powerpc: Clean up zImage handling of the command line 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=20070322013501.GG2295@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=miltonm@bga.com \
/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).