From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add more linux types
Date: Sun, 07 Sep 2008 00:04:50 +0200 [thread overview]
Message-ID: <20080906220450.B0180248BB@gemini.denx.de> (raw)
In-Reply-To: <20080829000751.GA5513@july>
Dear Kyungmin Park,
In message <20080829000751.GA5513@july> you wrote:
> It's preparation for UBI codes
>
> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> ---
> diff --git a/include/linux/types.h b/include/linux/types.h
> index df4808f..1b0b4a4 100644
> --- a/include/linux/types.h
> +++ b/include/linux/types.h
> @@ -119,6 +119,30 @@ typedef __s64 int64_t;
> * Below are truly Linux-specific types that should never collide with
> * any application/library that wants linux/types.h.
> */
> +#ifdef __CHECKER__
> +#define __bitwise__ __attribute__((bitwise))
> +#else
> +#define __bitwise__
> +#endif
> +#ifdef __CHECK_ENDIAN__
> +#define __bitwise __bitwise__
> +#else
> +#define __bitwise
> +#endif
> +
> +typedef __u16 __bitwise __le16;
> +typedef __u16 __bitwise __be16;
> +typedef __u32 __bitwise __le32;
> +typedef __u32 __bitwise __be32;
> +#if defined(__GNUC__)
> +typedef __u64 __bitwise __le64;
> +typedef __u64 __bitwise __be64;
> +#endif
> +typedef __u16 __bitwise __sum16;
> +typedef __u32 __bitwise __wsum;
> +
> +
> +typedef unsigned __bitwise__ gfp_t;
Please let's add such stuff as part of a patch series that also adds
actual users for these new definitions.
Rejected for now.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Why can you only have two doors on a chicken coop? If it had four it
would be a chicken sedan.
prev parent reply other threads:[~2008-09-06 22:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 0:07 [U-Boot] [PATCH] Add more linux types Kyungmin Park
2008-09-06 22:04 ` Wolfgang Denk [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=20080906220450.B0180248BB@gemini.denx.de \
--to=wd@denx.de \
--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