All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ksenija Stanojevic <ksenija.stanojevic@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH 2/4] Staging: lustre: include: Convert macro class_export_lock_get into static inline function
Date: Fri, 16 Oct 2015 22:28:29 -0700	[thread overview]
Message-ID: <20151017052829.GA30655@kroah.com> (raw)
In-Reply-To: <177dcb20f3ef1cbdc03ebee64223bb7e69811313.1444856328.git.ksenija.stanojevic@gmail.com>

On Wed, Oct 14, 2015 at 11:07:20PM +0200, Ksenija Stanojevic wrote:
> Static inline functions are preferred over macros. This change is safe
> because the types of arguments at all the call sites are same.
> 
> Signed-off-by: Ksenija Stanojevic<ksenija.stanojevic@gmail.com>
> ---
>  drivers/staging/lustre/lustre/include/obd_class.h | 17 +++++++++--------
>  1 file changed, 9 insertions(+), 8 deletions(-)

This, and patch 3/4, break the build very badly, did you test these
patches?

greg k-h


  reply	other threads:[~2015-10-17  5:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 21:04 [PATCH 0/4]Staging: lustre: Use static inline functions instead of macros Ksenija Stanojevic
2015-10-14 21:06 ` [PATCH 1/4] Staging: lustre: include: Move function prototypes Ksenija Stanojevic
2015-10-17  5:24   ` [Outreachy kernel] " Greg KH
2015-10-17  7:09     ` Ksenija Stanojević
2015-10-17  7:16       ` Greg KH
2015-10-14 21:07 ` [PATCH 2/4] Staging: lustre: include: Convert macro class_export_lock_get into static inline function Ksenija Stanojevic
2015-10-17  5:28   ` Greg KH [this message]
2015-10-17  7:10     ` [Outreachy kernel] " Ksenija Stanojević
2015-10-14 21:08 ` [PATCH 3/4] Staging: lustre: include: Convert macro class_export_lock_put " Ksenija Stanojevic
2015-10-14 21:09 ` [PATCH 4/4] Staging: lustre: include : Remove unused macros Ksenija Stanojevic

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=20151017052829.GA30655@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ksenija.stanojevic@gmail.com \
    --cc=outreachy-kernel@googlegroups.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.