From: Jon Loeliger <jdl@jdl.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Scott Wood <scottwood@freescale.com>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Add support for binary includes.
Date: Mon, 02 Jun 2008 15:22:40 -0500 [thread overview]
Message-ID: <E1K3GYC-0008F8-1v@jdl.com> (raw)
In-Reply-To: <20080530013418.GC26816@yookeroo.seuss>
> On Thu, May 29, 2008 at 09:04:29AM -0500, Jon Loeliger wrote:
> >
> > I believe I am fully caught up at this point.
>
> Not quite, this one slipped through the cracks:
Rats.
> dtc: Fix some printf() format warnings when compiling 64-bit
>
> Currently, dtc generates a few gcc build warnings if built for a
> 64-bit target, due to the altered type of uint64_t and size_t. This
> patch fixes the warnings (without generating new warnings for 32-bit).
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Please use git for your patches. Really.
Thanks,
jdl
prev parent reply other threads:[~2008-06-02 20:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 19:19 [PATCH] Add support for binary includes Scott Wood
2008-02-22 5:34 ` David Gibson
2008-02-22 18:12 ` Jon Loeliger
2008-02-25 3:38 ` David Gibson
2008-02-22 6:05 ` Grant Likely
2008-02-22 8:34 ` Bartlomiej Sieka
2008-02-22 9:02 ` David Woodhouse
2008-02-22 15:50 ` Grant Likely
2008-02-22 16:08 ` Scott Wood
2008-02-22 16:24 ` Jon Loeliger
2008-02-22 16:28 ` Scott Wood
2008-02-26 0:39 ` David Gibson
2008-02-26 17:26 ` Scott Wood
2008-05-27 15:27 ` Kumar Gala
2008-05-27 17:59 ` Jon Loeliger
2008-05-28 23:58 ` David Gibson
2008-05-29 0:02 ` David Gibson
2008-05-30 18:54 ` Scott Wood
2008-06-04 4:13 ` David Gibson
2008-06-04 12:36 ` Bartlomiej Sieka
2008-06-04 14:26 ` Jon Loeliger
2008-06-05 3:11 ` Josh Boyer
2008-06-11 1:58 ` dtc: " David Gibson
2008-06-12 16:43 ` Scott Wood
2008-06-13 0:01 ` David Gibson
2008-06-13 0:46 ` Jon Loeliger
2008-06-13 3:41 ` David Gibson
2008-05-29 14:04 ` [PATCH] " Jon Loeliger
2008-05-30 1:34 ` David Gibson
2008-06-02 20:22 ` 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=E1K3GYC-0008F8-1v@jdl.com \
--to=jdl@jdl.com \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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).