All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Aastha Gupta <aastha.gupta4104@gmail.com>
Cc: outreachy-kernel@googlegroups.com,
	Oleg Drokin <oleg.drokin@intel.com>,
	Andreas Dilger <andreas.dilger@intel.com>,
	James Simmons <jsimmons@infradead.org>
Subject: Re: [PATCH v3 03/10] staging: lustre: fix macro definitions warnings
Date: Wed, 18 Oct 2017 15:24:03 +0200	[thread overview]
Message-ID: <20171018132403.GA2934@kroah.com> (raw)
In-Reply-To: <1508328870-9416-4-git-send-email-aastha.gupta4104@gmail.com>

On Wed, Oct 18, 2017 at 05:44:23PM +0530, Aastha Gupta wrote:
> This patch fixes the checkpatch.pl warnings related to macro
> definitions.
> 1. macros with complex values should be enclosed in parentheses.
> 2. macros with multiple lines should be enclosed in do-while block.
> 
> Signed-off-by: Aastha Gupta <aastha.gupta4104@gmail.com>
> ---
>  drivers/staging/lustre/lustre/include/lu_object.h | 14 ++++++++------
>  1 file changed, 8 insertions(+), 6 deletions(-)

This is the patch that breaks the build, again, always test it before
sending it out.

Here is just one error from the build with this patch enabled, there
were lots and lots of others:

In file included from ./drivers/staging/lustre/lustre/include/lustre_net.h:63:0,
                 from ./drivers/staging/lustre/lustre/include/obd_class.h:37,
                 from drivers/staging/lustre/lustre/osc/osc_dev.c:40:
./drivers/staging/lustre/lustre/include/lu_object.h:1226:1: error: expected identifier or ‘(’ before ‘do’
 do {      \
 ^
drivers/staging/lustre/lustre/osc/osc_dev.c:159:1: note: in expansion of macro ‘LU_TYPE_INIT_FINI’
 LU_TYPE_INIT_FINI(osc, &osc_key, &osc_session_key);
 ^~~~~~~~~~~~~~~~~
./drivers/staging/lustre/lustre/include/lu_object.h:1231:3: error: expected identifier or ‘(’ before ‘while’
 } while (0)
   ^
drivers/staging/lustre/lustre/osc/osc_dev.c:159:1: note: in expansion of macro ‘LU_TYPE_INIT_FINI’
 LU_TYPE_INIT_FINI(osc, &osc_key, &osc_session_key);
 ^~~~~~~~~~~~~~~~~

I've applied the first 2 patches in this series, so please fix and rebase and
resend the rest.

thanks,

greg k-h


  reply	other threads:[~2017-10-18 13:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18 12:14 [PATCH v3 00/10] staging: lustre: fix code styling issues and remove macros without users Aastha Gupta
2017-10-18 12:14 ` [PATCH v3 01/10] staging: lustre: fix incorrect multi-line comment style Aastha Gupta
2017-10-18 12:14 ` [PATCH v3 02/10] staging: lustre: fix comparisons should place the constant on the right side Aastha Gupta
2017-10-18 12:14 ` [PATCH v3 03/10] staging: lustre: fix macro definitions warnings Aastha Gupta
2017-10-18 13:24   ` Greg Kroah-Hartman [this message]
2017-10-18 12:14 ` [PATCH v3 04/10] staging: lustre: drop macro that has no uses Aastha Gupta
2017-10-18 12:14 ` [PATCH v3 05/10] staging: lustre: fid: fix line over 80 characters Aastha Gupta
2017-10-18 12:14 ` [PATCH v3 06/10] staging: lustre: fld: " Aastha Gupta
2017-10-18 12:14 ` [PATCH v3 07/10] staging: lustre: ldlm: fix lines over 80 characters in ldlm files Aastha Gupta
2017-10-18 12:14 ` [PATCH v3 08/10] staging: lustre: llite: fix lines over 80 characters in llite files Aastha Gupta
2017-10-18 12:14 ` [PATCH v3 09/10] staging: lustre: llite: fix coding style for error messages Aastha Gupta
2017-10-18 12:14 ` [PATCH v3 10/10] staging: lustre: lllite: fix multi line comments style Aastha Gupta
2017-10-18 12:36 ` [PATCH v3 00/10] staging: lustre: fix code styling issues and remove macros without users Greg Kroah-Hartman

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=20171018132403.GA2934@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=aastha.gupta4104@gmail.com \
    --cc=andreas.dilger@intel.com \
    --cc=jsimmons@infradead.org \
    --cc=oleg.drokin@intel.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.