reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Elder <alex.elder@linaro.org>
To: Sage Weil <sage@inktank.com>, David Miller <davem@davemloft.net>,
	kuznet@ms2.inr.ac.ru, jmorris@namei.org, yoshfuji@linux-ipv6.org,
	kaber@trash.net, Al Viro <viro@ZenIV.linux.org.uk>,
	jeffm@suse.com, Steven Rostedt <rostedt@goodmis.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	mst@redhat.com, Ingo Molnar <mingo@kernel.org>
Cc: reiserfs-devel@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	ceph-devel <ceph-devel@vger.kernel.org>,
	netdev@vger.kernel.org
Subject: [PATCH 0/3] kernel.h: centrally define U32_MAX, etc.
Date: Thu, 26 Dec 2013 09:11:28 -0600	[thread overview]
Message-ID: <52BC4720.1070904@linaro.org> (raw)

Although types u32, s32, u16, s16 and so on are fundamental kernel
types, there is no central symbolic definition of their maximum and
minimum values.  In the past I've added and used such definitions
where I've needed them but they really belong in "kernel.h".

This series does this, in three steps.  The first makes existing
definitions be done conditionally; the second defines them in
"kernel.h"; and the third gets rid of the conditional definitions.

(These three can obviously be squashed into a single commit.)

    					-Alex

Alex Elder (3):
  conditionally define U32_MAX
  kernel.h: define u8, s8, u32, etc. limits
  remove extra definitions of U32_MAX

 fs/reiserfs/reiserfs.h      |    2 --
 include/linux/ceph/decode.h |   17 -----------------
 include/linux/kernel.h      |   13 +++++++++++++
 net/ipv4/tcp_illinois.c     |    1 -
 4 files changed, 13 insertions(+), 20 deletions(-)

-- 
1.7.9.5

                 reply	other threads:[~2013-12-26 15:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=52BC4720.1070904@linaro.org \
    --to=alex.elder@linaro.org \
    --cc=akpm@linux-foundation.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=jeffm@suse.com \
    --cc=jmorris@namei.org \
    --cc=kaber@trash.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sage@inktank.com \
    --cc=viro@ZenIV.linux.org.uk \
    --cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).