From: Masahiro Yamada <yamada.m@jp.panasonic.com>
To: barebox@lists.infradead.org
Subject: [PATCH 1/5] fs: ubifs: remove redundant macro defines
Date: Wed, 21 Jan 2015 14:09:15 +0900 [thread overview]
Message-ID: <1421816959-19004-2-git-send-email-yamada.m@jp.panasonic.com> (raw)
In-Reply-To: <1421816959-19004-1-git-send-email-yamada.m@jp.panasonic.com>
fs/ubifs/ubifs.h includes <common.h> and the macros INT_MAX, INT_MIN,
LLONG_MAX are already defined there.
The same defines in fs/ubifs/ubifs.h are redundant.
Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
---
fs/ubifs/ubifs.h | 4 ----
1 file changed, 4 deletions(-)
diff --git a/fs/ubifs/ubifs.h b/fs/ubifs/ubifs.h
index b4a9d76..c025d34 100644
--- a/fs/ubifs/ubifs.h
+++ b/fs/ubifs/ubifs.h
@@ -318,10 +318,6 @@ struct file {
#define MAX_LFS_FILESIZE 0x7fffffffffffffffUL
#endif
-#define INT_MAX ((int)(~0U>>1))
-#define INT_MIN (-INT_MAX - 1)
-#define LLONG_MAX ((long long)(~0ULL>>1))
-
/*
* These are the fs-independent mount-flags: up to 32 flags are supported
*/
--
1.9.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-01-21 5:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 5:09 [PATCH 0/5] rafactor _*MAX, *_MIN macros Masahiro Yamada
2015-01-21 5:09 ` Masahiro Yamada [this message]
2015-01-21 5:09 ` [PATCH 2/5] lib: decompress: remove redundant INT_MAX define Masahiro Yamada
2015-01-21 5:09 ` [PATCH 3/5] linux/kernel.h: move *_MAX, *_MIN macros Masahiro Yamada
2015-01-21 5:09 ` [PATCH 4/5] linux/kernel.h: rename USHORT_MAX, SHORT_MAX, SHORT_MIN Masahiro Yamada
2015-01-21 5:09 ` [PATCH 5/5] linux/kernel.h: add more *_MAX, *_MIN macros Masahiro Yamada
2015-01-21 6:30 ` [PATCH 0/5] rafactor _*MAX, " Jean-Christophe PLAGNIOL-VILLARD
2015-01-21 13:59 ` Sascha Hauer
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=1421816959-19004-2-git-send-email-yamada.m@jp.panasonic.com \
--to=yamada.m@jp.panasonic.com \
--cc=barebox@lists.infradead.org \
/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