From: Raja R Harinath <harinath@hurrynot.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kmemcheck: fix sparse warning
Date: Thu, 06 Aug 2009 18:06:41 +0530 [thread overview]
Message-ID: <87r5vpyv8m.fsf@hariville.hurrynot.org> (raw)
In-Reply-To: 1248874951.25614.0.camel@johannes.local
Hi,
Johannes Berg <johannes@sipsolutions.net> writes:
>> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
I know I'm colouring the bike-shed but you can avoid the outer do-while
with:
>> --- 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) { \
+ 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)
+ } else
Of course, that tailing 'else' may be much too clever to live. A
slightly less clever but more idiomatic approach would be to use
+ } else do {} while (0)
but what's the point. Oh well, ignore me :-) I'm just pained by the
'} }' due to my wierd sense of aesthetics.
- Hari
prev parent reply other threads:[~2009-08-06 12:39 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
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 [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=87r5vpyv8m.fsf@hariville.hurrynot.org \
--to=harinath@hurrynot.org \
--cc=linux-kernel@vger.kernel.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 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.