From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/3] Add limits.h to hold basic limits
Date: Fri, 21 Oct 2011 21:54:21 +0200 [thread overview]
Message-ID: <4EA1CDED.8060604@aribaud.net> (raw)
In-Reply-To: <1318274551-25335-2-git-send-email-sjg@chromium.org>
Hi Simon,
Le 10/10/2011 21:22, Simon Glass a ?crit :
> This brings a basic limits.h implementation into U-Boot.
>
> Signed-off-by: Simon Glass<sjg@chromium.org>
> ---
> fs/ubifs/ubifs.h | 4 +---
> include/limits.h | 40 ++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 41 insertions(+), 3 deletions(-)
> create mode 100644 include/limits.h
Apparently, in all the U-Boot codebase, only one file required standard
limit names, and gets them with three lines of code. Is it worth adding
40 lines of code for this?
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-10-21 19:54 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 [this message]
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
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=4EA1CDED.8060604@aribaud.net \
--to=albert.u.boot@aribaud.net \
--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