From: Jeremiah Mahler <jmmahler@gmail.com>
To: Oleg Drokin <oleg.drokin@intel.com>
Cc: Andreas Dilger <andreas.dilger@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Peng Tao <bergwolf@gmail.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Julia Lawall <Julia.Lawall@lip6.fr>,
Kirill Tkhai <ktkhai@parallels.com>,
Joe Perches <joe@perches.com>, Zi Shen Lim <zlim.lnx@gmail.com>,
Dmitry Eremin <dmitry.eremin@intel.com>,
Masaru Nomura <massa.nomura@gmail.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
James A Shackleford <shack@linux.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Jeremiah Mahler <jmmahler@gmail.com>
Subject: [PATCH 0/6] staging: lustre: use built in min/max functions
Date: Thu, 25 Dec 2014 16:04:40 -0800 [thread overview]
Message-ID: <1419552286-8492-1-git-send-email-jmmahler@gmail.com> (raw)
The lustre modules define their own custom MIN, MAX and min_t functions.
However Linux provides these functions (include/linux/kernel.h) and their
design is more robust. They check types and produce compiler warnings
if differing types are used.
This patch set updates the lustre modules to use the built in min/max
functions.
Jeremiah Mahler (6):
staging: lustre: use min/max instead of MIN/MAX, simple cases
staging: lustre: replace MIN with min_t
staging: lustre: replace MIN/MAX with min_t/max_t
staging: lustre: replace MIN with min, cast (__kernel_size_t)
staging: lustre: replace MIN with min_t, remove cast
staging: lustre: remove custom MIN/MAX and min_t operations
.../lustre/include/linux/libcfs/libcfs_private.h | 8 --------
.../staging/lustre/lnet/klnds/o2iblnd/o2iblnd_cb.c | 2 +-
drivers/staging/lustre/lnet/klnds/socklnd/socklnd.c | 2 +-
.../staging/lustre/lnet/klnds/socklnd/socklnd_cb.c | 6 +++---
drivers/staging/lustre/lnet/lnet/lib-move.c | 20 ++++++++++----------
drivers/staging/lustre/lnet/lnet/router.c | 4 ++--
drivers/staging/lustre/lnet/lnet/router_proc.c | 2 +-
drivers/staging/lustre/lnet/selftest/conrpc.h | 2 +-
drivers/staging/lustre/lnet/selftest/rpc.c | 4 ++--
.../lustre/lustre/libcfs/linux/linux-tracefile.c | 2 +-
drivers/staging/lustre/lustre/osc/osc_internal.h | 5 -----
11 files changed, 22 insertions(+), 35 deletions(-)
--
2.1.4
next reply other threads:[~2014-12-26 0:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 0:04 Jeremiah Mahler [this message]
2014-12-26 0:04 ` [PATCH 1/6] staging: lustre: use min/max instead of MIN/MAX, simple cases Jeremiah Mahler
2014-12-26 0:04 ` [PATCH 2/6] staging: lustre: replace MIN with min_t Jeremiah Mahler
2014-12-26 0:04 ` [PATCH 3/6] staging: lustre: replace MIN/MAX with min_t/max_t Jeremiah Mahler
2014-12-26 0:04 ` [PATCH 4/6] staging: lustre: replace MIN with min, cast (__kernel_size_t) Jeremiah Mahler
2014-12-26 0:04 ` [PATCH 5/6] staging: lustre: replace MIN with min_t, remove cast Jeremiah Mahler
2014-12-26 0:04 ` [PATCH 6/6] staging: lustre: remove custom MIN/MAX and min_t operations Jeremiah Mahler
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=1419552286-8492-1-git-send-email-jmmahler@gmail.com \
--to=jmmahler@gmail.com \
--cc=Julia.Lawall@lip6.fr \
--cc=andreas.dilger@intel.com \
--cc=bergwolf@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=dmitry.eremin@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=ktkhai@parallels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=massa.nomura@gmail.com \
--cc=oleg.drokin@intel.com \
--cc=peterz@infradead.org \
--cc=shack@linux.com \
--cc=zlim.lnx@gmail.com \
/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
all inboxes | Powered by JetHome®