From: Sergei Zviagintsev <sergei@s15v.net>
To: David Herrmann <dh.herrmann@gmail.com>
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>
Subject: Re: [PATCH] kdbus: use parentheses in KDBUS_ITEM_FOREACH macro uniformly
Date: Thu, 4 Jun 2015 14:47:43 +0300 [thread overview]
Message-ID: <20150604114743.GE4549@localhost.localdomain> (raw)
In-Reply-To: <CANq1E4S4vy+BTnj=ifd0NSE3DoSc=aS998Lqt-GCWe5TAXWQyw@mail.gmail.com>
Hi David,
On Thu, Jun 04, 2015 at 01:29:22PM +0200, David Herrmann wrote:
> 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.
I agree, the point is just to keep things consistent. I'll send v2.
> 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
> >
prev parent reply other threads:[~2015-06-04 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 10:39 [PATCH] kdbus: use parentheses in KDBUS_ITEM_FOREACH macro uniformly Sergei Zviagintsev
2015-06-04 11:29 ` David Herrmann
2015-06-04 11:47 ` Sergei Zviagintsev [this message]
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=20150604114743.GE4549@localhost.localdomain \
--to=sergei@s15v.net \
--cc=daniel@zonque.org \
--cc=dh.herrmann@gmail.com \
--cc=dh.herrmann@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tixxdz@opendz.org \
/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