All of lore.kernel.org
 help / color / mirror / Atom feed
From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [Patch v3] Consolidate bool type
Date: Wed, 23 Jan 2013 13:46:04 -0800	[thread overview]
Message-ID: <51005A1C.1010308@freescale.com> (raw)
In-Reply-To: <1358977307-17350-1-git-send-email-yorksun@freescale.com>

On 01/23/2013 01:41 PM, York Sun wrote:
> 'bool' is defined in random places. This patch consolidates them into a
> single header file include/linux/types.h, using stdbool.h.
> 
> All other #define, typedef and enum are removed. They are all consistent with
> true = 1, false = 0.
> 
> Signed-off-by: York Sun <yorksun@freescale.com>
> ---
> Change since v1:
>  Move 'false' and 'true' to the common header file.
> 
> Change since v2:
>  Use stdbool.h
>  Consolidate all TRUE, FALSE, True, False, true, false
> 
> Need help to test on all ARCHs with differnt toolchains as well as USE_PRIVATE_LIBGCC.
> 
>
I should put RFC in the subject as I am not able to compile all ARCH myself.

York

  reply	other threads:[~2013-01-23 21:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 21:41 [U-Boot] [Patch v3] Consolidate bool type York Sun
2013-01-23 21:46 ` York Sun [this message]
2013-01-23 21:52   ` Scott Wood
2013-01-23 22:01     ` York Sun
2013-01-23 22:02       ` Scott Wood
2013-01-23 22:05         ` York Sun
2013-01-23 22:10           ` Allen Martin
2013-01-24 17:34           ` Allen Martin
2013-01-24 17:54             ` York Sun
2013-01-24 18:03               ` York Sun
2013-01-24 18:14                 ` Scott Wood
2013-01-24 18:23                   ` York Sun
2013-01-24 18:28                     ` Allen Martin
2013-01-24 18:49                       ` York Sun
2013-01-24 18:25                   ` Allen Martin
2013-01-24 18:26                 ` Wolfgang Denk
2013-01-23 21:53 ` Scott Wood
2013-01-23 22:04   ` York Sun

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=51005A1C.1010308@freescale.com \
    --to=yorksun@freescale.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.