From: Josh Durgin <josh.durgin@inktank.com>
To: Alex Elder <elder@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: [PATCH] rbd: add parentheses to object request iterator macros
Date: Tue, 19 Feb 2013 11:15:24 -0800 [thread overview]
Message-ID: <5123CF4C.7090305@inktank.com> (raw)
In-Reply-To: <51152572.1060602@inktank.com>
Reviewed-by: Josh Durgin <josh.durgin@inktank.com>
On 02/08/2013 08:18 AM, Alex Elder wrote:
> The for_each_obj_request*() macros should parenthesize their uses of
> the ireq parameter.
>
> Signed-off-by: Alex Elder <elder@inktank.com>
> ---
> drivers/block/rbd.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/block/rbd.c b/drivers/block/rbd.c
> index 982963e..6e9e2c2 100644
> --- a/drivers/block/rbd.c
> +++ b/drivers/block/rbd.c
> @@ -226,11 +226,11 @@ struct rbd_img_request {
> };
>
> #define for_each_obj_request(ireq, oreq) \
> - list_for_each_entry(oreq, &ireq->obj_requests, links)
> + list_for_each_entry(oreq, &(ireq)->obj_requests, links)
> #define for_each_obj_request_from(ireq, oreq) \
> - list_for_each_entry_from(oreq, &ireq->obj_requests, links)
> + list_for_each_entry_from(oreq, &(ireq)->obj_requests, links)
> #define for_each_obj_request_safe(ireq, oreq, n) \
> - list_for_each_entry_safe_reverse(oreq, n, &ireq->obj_requests, links)
> + list_for_each_entry_safe_reverse(oreq, n, &(ireq)->obj_requests, links)
>
> struct rbd_snap {
> struct device dev;
>
prev parent reply other threads:[~2013-02-19 19:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 16:18 [PATCH] rbd: add parentheses to object request iterator macros Alex Elder
2013-02-19 19:15 ` Josh Durgin [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=5123CF4C.7090305@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=elder@inktank.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.