All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kmemcheck: fix sparse warning
Date: Mon, 06 Jul 2009 20:15:33 +0300	[thread overview]
Message-ID: <4A523135.40408@cs.helsinki.fi> (raw)
In-Reply-To: <1246873983.20908.0.camel@johannes.local>

Johannes Berg wrote:
> Whether or not the sparse warning
> 
> warning: do-while statement is not a compound statement
> 
> is justified or not in this case, it is annoying and
> trivial to fix.
> 
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>

Looks good to me!

Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>

> ---
>  include/linux/kmemcheck.h |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> --- wireless-testing.orig/include/linux/kmemcheck.h	2009-07-06 11:41:16.000000000 +0200
> +++ wireless-testing/include/linux/kmemcheck.h	2009-07-06 11:41:30.000000000 +0200
> @@ -137,13 +137,13 @@ static inline void kmemcheck_mark_initia
>  	int name##_end[0];
>  
>  #define kmemcheck_annotate_bitfield(ptr, name)				\
> -	do if (ptr) {							\
> +	do { if (ptr) {							\
>  		int _n = (long) &((ptr)->name##_end)			\
>  			- (long) &((ptr)->name##_begin);		\
>  		BUILD_BUG_ON(_n < 0);					\
>  									\
>  		kmemcheck_mark_initialized(&((ptr)->name##_begin), _n);	\
> -	} while (0)
> +	} } while (0)
>  
>  #define kmemcheck_annotate_variable(var)				\
>  	do {								\
> 
> 


  reply	other threads:[~2009-07-06 17:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06  9:53 [PATCH] kmemcheck: fix sparse warning Johannes Berg
2009-07-06 17:15 ` Pekka Enberg [this message]
2009-07-08 19:28 ` Vegard Nossum
2009-07-08 19:28   ` Vegard Nossum
2009-07-08 19:39   ` Johannes Berg
2009-07-08 20:28     ` Christopher Li
2009-07-09  6:29   ` Josh Triplett
2009-07-09  7:00     ` Hannes Eder
2009-07-09  7:00       ` Hannes Eder
2009-07-09  9:48     ` Bernd Petrovitsch
2009-07-29 13:42 ` Johannes Berg
2009-08-01 15:17   ` Pekka Enberg
2009-08-06 12:36   ` Raja R Harinath

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=4A523135.40408@cs.helsinki.fi \
    --to=penberg@cs.helsinki.fi \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vegard.nossum@gmail.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.