From: "greg@kroah.com" <greg@kroah.com>
To: Rishiraj Manwatkar <manwatkar@outlook.com>
Cc: "lustre-devel@lists.lustre.org" <lustre-devel@lists.lustre.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"andreas.dilger@intel.com" <andreas.dilger@intel.com>,
"oleg.drokin@intel.com" <oleg.drokin@intel.com>
Subject: Re: [Patch v2 1/2] lustre: Parantheses added for Macro argument to avoid precedence issues
Date: Sat, 15 Apr 2017 13:48:51 +0200 [thread overview]
Message-ID: <20170415114851.GA24035@kroah.com> (raw)
In-Reply-To: <VI1PR0901MB1616DC70D6D5F1A84A43C5D9A4040@VI1PR0901MB1616.eurprd09.prod.outlook.com>
On Sat, Apr 15, 2017 at 11:25:00AM +0000, Rishiraj Manwatkar wrote:
> From: RishirajAM <manwatkar@outlook.com>
>
> Parantheses are added for Macro argument, to avoid precedence issues.
>
> Signed-off-by: Rishiraj Manwatkar <manwatkar@outlook.com>
> ---
> drivers/staging/lustre/lustre/obdclass/cl_io.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
What changed from v1? Always put that below the --- line.
And your From: line doesn't match your signed-off-by name, that's not
ok.
>
> diff --git a/drivers/staging/lustre/lustre/obdclass/cl_io.c b/drivers/staging/lustre/lustre/obdclass/cl_io.c
> index ee7d677..0997254 100755
> --- a/drivers/staging/lustre/lustre/obdclass/cl_io.c
> +++ b/drivers/staging/lustre/lustre/obdclass/cl_io.c
> @@ -52,9 +52,9 @@
> */
>
> #define cl_io_for_each(slice, io) \
> - list_for_each_entry((slice), &io->ci_layers, cis_linkage)
> + list_for_each_entry((slice), &(io)->ci_layers, cis_linkage)
What 'precidence' issue is this fixing? How could that ever be
incorrect?
Really, this macro just needs to go away and be used "as is" anyway...
thanks,
greg k-h
parent reply other threads:[~2017-04-15 11:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <VI1PR0901MB1616DC70D6D5F1A84A43C5D9A4040@VI1PR0901MB1616.eurprd09.prod.outlook.com>]
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=20170415114851.GA24035@kroah.com \
--to=greg@kroah.com \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=manwatkar@outlook.com \
--cc=oleg.drokin@intel.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®