Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753244AbbFDL31 (ORCPT <rfc822;w@1wt.eu>);
	Thu, 4 Jun 2015 07:29:27 -0400
Received: from mail-lb0-f174.google.com ([209.85.217.174]:34848 "EHLO
	mail-lb0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751373AbbFDL3X (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Thu, 4 Jun 2015 07:29:23 -0400
MIME-Version: 1.0
In-Reply-To: <1433414370-17557-2-git-send-email-sergei@s15v.net>
References: <1433414370-17557-2-git-send-email-sergei@s15v.net>
Date: Thu, 4 Jun 2015 13:29:22 +0200
Message-ID: <CANq1E4S4vy+BTnj=ifd0NSE3DoSc=aS998Lqt-GCWe5TAXWQyw@mail.gmail.com>
Subject: Re: [PATCH] kdbus: use parentheses in KDBUS_ITEM_FOREACH macro uniformly
From: David Herrmann <dh.herrmann@gmail.com>
To: Sergei Zviagintsev <sergei@s15v.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Daniel Mack <daniel@zonque.org>,
        David Herrmann <dh.herrmann@googlemail.com>,
        Djalal Harouni <tixxdz@opendz.org>,
        linux-kernel <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 2953
Lines: 67

Hi

On Thu, Jun 4, 2015 at 12:39 PM, Sergei Zviagintsev <sergei@s15v.net> wrote:
> _i is used as loop cursor and must be a proper lvalue, whereas two other
> arguments can be complex expressions. Stay uniform across the macro and
> enclose _is and _s with parentheses in all cases, but keep _i without
> them (any valid lvalue will not break cast to (u8 *) due to precedence
> rules). Update documentation example.
>
> List macroses (e.g. list_for_each) were taken as an example for this
> change.

I'm not a big fan of this patch. Treating arguments differently just
makes the macros harder to read, imo. Why not keep the parantheses
around all arguments? It doesn't hurt and keeps the style consistent.
Besides, lvalues might consist of more complex expressions, so I'm not
sure this is even the right way to go.

Thanks
David

> Signed-off-by: Sergei Zviagintsev <sergei@s15v.net>
> ---
>  Documentation/kdbus/kdbus.item.xml | 4 ++--
>  ipc/kdbus/item.h                   | 6 +++---
>  2 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/kdbus/kdbus.item.xml b/Documentation/kdbus/kdbus.item.xml
> index b0eeeef995af..fb8b6c151a0d 100644
> --- a/Documentation/kdbus/kdbus.item.xml
> +++ b/Documentation/kdbus/kdbus.item.xml
> @@ -73,8 +73,8 @@
>
>  #define KDBUS_ITEM_FOREACH(item, head, first)                      \
>      for (item = (head)->first;                                     \
> -         ((uint8_t *)(item) < (uint8_t *)(head) + (head)->size) && \
> -          ((uint8_t *)(item) >= (uint8_t *)(head));                \
> +         ((uint8_t *)item < (uint8_t *)(head) + (head)->size) &&   \
> +          ((uint8_t *)item >= (uint8_t *)(head));                \
>           item = KDBUS_ITEM_NEXT(item))
>        ]]></programlisting>
>      </refsect2>
> diff --git a/ipc/kdbus/item.h b/ipc/kdbus/item.h
> index 03612368b3bb..592b68a7c2db 100644
> --- a/ipc/kdbus/item.h
> +++ b/ipc/kdbus/item.h
> @@ -28,9 +28,9 @@
>  #define KDBUS_ITEM_PAYLOAD_SIZE(_i) ((_i)->size - KDBUS_ITEM_HEADER_SIZE)
>
>  #define KDBUS_ITEMS_FOREACH(_i, _is, _s)                               \
> -       for (_i = _is;                                                  \
> -            ((u8 *)(_i) < (u8 *)(_is) + (_s)) &&                       \
> -              ((u8 *)(_i) >= (u8 *)(_is));                             \
> +       for (_i = (_is);                                                \
> +            ((u8 *)_i < (u8 *)(_is) + (_s)) &&                         \
> +              ((u8 *)_i >= (u8 *)(_is));                               \
>              _i = KDBUS_ITEM_NEXT(_i))
>
>  #define KDBUS_ITEM_VALID(_i, _is, _s)                                  \
> --
> 1.8.3.1
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/