From: Joe Perches <joe@perches.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Borislav Petkov <bp@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Andres Freund <andres@anarazel.de>,
x86@kernel.org, linux-kernel@vger.kernel.org,
"H. Peter Anvin" <hpa@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
Andy Whitcroft <apw@canonical.com>
Subject: Re: [PATCH] checkpatch: Warn on #defines ending in semicolon
Date: Fri, 09 May 2014 14:59:48 -0700 [thread overview]
Message-ID: <1399672788.2912.32.camel@joe-AO725> (raw)
In-Reply-To: <alpine.DEB.2.02.1405092345480.6261@ionos.tec.linutronix.de>
On Fri, 2014-05-09 at 23:47 +0200, Thomas Gleixner wrote:
> On Fri, 9 May 2014, Joe Perches wrote:
>
> > Using a #define ending in a semicolon is poor style
>
> It's not poor style it's simply a bug. Just because it
>
> > can lead to unexpected code paths being executed.
I think it's still a (bad) style issue.
I remember a discussion with a developer that
wanted all macros to end in a semicolon so he
could write COBOL like C.
ick.
cheers, Joe
next prev parent reply other threads:[~2014-05-09 21:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 1:29 Andres Freund
2014-05-09 1:29 ` [PATCH 1/2] x86: Fix typo preventing msr_set/clear_bit from having an effect Andres Freund
2014-05-09 7:54 ` Borislav Petkov
2014-05-09 10:39 ` Andres Freund
2014-05-09 10:46 ` Borislav Petkov
2014-05-09 16:31 ` [tip:x86/urgent] x86: Fix typo preventing msr_set/ clear_bit " tip-bot for Andres Freund
2014-05-09 1:29 ` [PATCH 2/2] x86: Fix typo in MSR_IA32_MISC_ENABLE_LIMIT_CPUID macro Andres Freund
2014-05-09 7:57 ` Borislav Petkov
2014-05-09 10:33 ` Borislav Petkov
2014-05-09 17:02 ` Joe Perches
2014-05-09 21:31 ` [PATCH] checkpatch: Warn on #defines ending in semicolon Joe Perches
2014-05-09 21:47 ` Thomas Gleixner
2014-05-09 21:59 ` Joe Perches [this message]
2014-05-09 16:31 ` [tip:x86/urgent] x86: Fix typo in MSR_IA32_MISC_ENABLE_LIMIT_CPUID macro tip-bot for Andres Freund
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=1399672788.2912.32.camel@joe-AO725 \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=andres@anarazel.de \
--cc=apw@canonical.com \
--cc=bp@suse.de \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®