From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/3] Add limits.h to hold basic limits
Date: Thu, 3 Nov 2011 22:33:38 -0400 [thread overview]
Message-ID: <201111032233.39073.vapier@gentoo.org> (raw)
In-Reply-To: <1318274551-25335-2-git-send-email-sjg@chromium.org>
On Monday 10 October 2011 15:22:29 Simon Glass wrote:
> This brings a basic limits.h implementation into U-Boot.
sorry to jump in so late, but i think this was the correct way to go. copying
& pasting the same defines throughout the tree doesn't make much sense. this
would also make it easier to grab changes from Linux since they're the same.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20111103/bd24884e/attachment.pgp
next prev parent reply other threads:[~2011-11-04 2:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 19:22 [U-Boot] [PATCH v2 0/3] Buffer overruns in printf Simon Glass
2011-10-10 19:22 ` [U-Boot] [PATCH v2 1/3] Add limits.h to hold basic limits Simon Glass
2011-10-21 19:54 ` Albert ARIBAUD
2011-10-21 20:19 ` Simon Glass
2011-10-21 21:00 ` Albert ARIBAUD
2011-10-21 21:12 ` Simon Glass
2011-10-21 21:47 ` Albert ARIBAUD
2011-10-21 22:02 ` Simon Glass
2011-10-21 22:39 ` Albert ARIBAUD
2011-10-22 4:58 ` Simon Glass
2011-10-25 23:43 ` Simon Glass
2011-11-04 2:33 ` Mike Frysinger [this message]
2011-11-04 5:14 ` Simon Glass
2011-11-04 23:09 ` Mike Frysinger
2011-11-05 0:24 ` Simon Glass
2011-10-10 19:22 ` [U-Boot] [PATCH v2 2/3] Add safe vsnprintf and snprintf library functions Simon Glass
2011-10-10 19:22 ` [U-Boot] [PATCH v2 3/3] Make printf and vprintf safe from buffer overruns Simon Glass
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=201111032233.39073.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox