From: Segher Boessenkool <segher@kernel.crashing.org>
To: Andy Whitcroft <apw@shadowen.org>
Cc: Paul Jackson <pj@sgi.com>, Rogan Dawes <lists@dawes.za.net>,
Jan Engelhardt <jengelh@computergmbh.de>,
linux-kernel@vger.kernel.org
Subject: Re: +patch Why these dot chars in scripts/checkpatch.pl?
Date: Tue, 29 Apr 2008 11:51:52 +0200 [thread overview]
Message-ID: <bbde4dbb04c0d77f846f0ed706a81530@kernel.crashing.org> (raw)
In-Reply-To: <20080428230637.GX5401@shadowen.org>
> Yeah I was under the missaprehension that whitespace was allowed after
> the # but not before. That seems to be flawed.
It is true for K&R C (so with -traditional cpp mode), but indeed
false for ISO C.
Segher
next prev parent reply other threads:[~2008-04-29 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 20:31 Why these dot chars in scripts/checkpatch.pl? Paul Jackson
2008-04-28 20:47 ` Rogan Dawes
2008-04-28 20:51 ` Paul Jackson
2008-04-28 22:10 ` Jan Engelhardt
2008-04-28 23:06 ` +patch " Andy Whitcroft
2008-04-29 9:51 ` Segher Boessenkool [this message]
2008-04-28 23:02 ` Andy Whitcroft
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=bbde4dbb04c0d77f846f0ed706a81530@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=apw@shadowen.org \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@dawes.za.net \
--cc=pj@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox