From: Christoph Hellwig <hch@lst.de>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] fixup Documentation/DocBook/kernel-hacking.tmpl
Date: Tue, 20 Sep 2005 22:48:07 +0200 [thread overview]
Message-ID: <20050920204807.GA8538@lst.de> (raw)
__FUNCTION__ is the prefered kernel idiom, __func__ is not supported by
gcc 2.95 (we actually map __FUNCTION__ to __func__ for more recent
compilers, but it should never be used directly)
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: linux-2.6/Documentation/DocBook/kernel-hacking.tmpl
===================================================================
--- linux-2.6.orig/Documentation/DocBook/kernel-hacking.tmpl 2005-09-11 15:19:18.000000000 +0200
+++ linux-2.6/Documentation/DocBook/kernel-hacking.tmpl 2005-09-15 13:38:06.000000000 +0200
@@ -1105,7 +1105,7 @@
</listitem>
<listitem>
<para>
- Function names as strings (__func__).
+ Function names as strings (__FUNCTION__).
</para>
</listitem>
<listitem>
reply other threads:[~2005-09-20 20:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050920204807.GA8538@lst.de \
--to=hch@lst.de \
--cc=akpm@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox