From: Greg KH <gregkh@linuxfoundation.org>
To: Shivani Bhardwaj <shivanib134@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH] Staging: lustre: interval_tree: Convert inline function to macro
Date: Sat, 31 Oct 2015 11:53:00 -0700 [thread overview]
Message-ID: <20151031185300.GA8949@kroah.com> (raw)
In-Reply-To: <20151031184544.GA27064@ubuntu>
On Sun, Nov 01, 2015 at 12:15:44AM +0530, Shivani Bhardwaj wrote:
> Convert the function max_u64() to macro because macros tend to be more
> flexible than inline functions and here, the macro is going to be type
> safe so there are not going to be any side effects.
>
> Signed-off-by: Shivani Bhardwaj <shivanib134@gmail.com>
> ---
> drivers/staging/lustre/lustre/ldlm/interval_tree.c | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/staging/lustre/lustre/ldlm/interval_tree.c b/drivers/staging/lustre/lustre/ldlm/interval_tree.c
> index a2ea8e5..52d0afd 100644
> --- a/drivers/staging/lustre/lustre/ldlm/interval_tree.c
> +++ b/drivers/staging/lustre/lustre/ldlm/interval_tree.c
> @@ -42,6 +42,8 @@
> #include "../include/obd_support.h"
> #include "../include/interval_tree.h"
>
> +#define max_u64(x, y) ((x > y) ? x : y)
Ick, no, there is already a _correct_ macro in the kernel for this,
don't try to create another one that does not work properly for all
users.
And your patch is also backwards, inline functions are better than
macros, don't ever convert from an inline function to a macro.
thanks,
greg k-h
next prev parent reply other threads:[~2015-10-31 18:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-31 18:45 [PATCH] Staging: lustre: interval_tree: Convert inline function to macro Shivani Bhardwaj
2015-10-31 18:53 ` Greg KH [this message]
2015-10-31 18:54 ` [Outreachy kernel] " Shivani Bhardwaj
2015-10-31 19:09 ` Julia Lawall
2015-10-31 19:12 ` Shivani Bhardwaj
2015-10-31 19:15 ` Julia Lawall
2015-10-31 19:27 ` Shivani Bhardwaj
2015-10-31 19:36 ` Julia Lawall
2015-10-31 19:38 ` Shivani Bhardwaj
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=20151031185300.GA8949@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=shivanib134@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 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.