From: Randy Dunlap <randy.dunlap@oracle.com>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Russell King <rmk@arm.linux.org.uk>, Greg KH <greg@kroah.com>,
Paul Mackerras <paulus@samba.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] misc: replace remaining __FUNCTION__ with __func__
Date: Mon, 20 Oct 2008 16:02:06 -0700 [thread overview]
Message-ID: <48FD0DEE.7000302@oracle.com> (raw)
In-Reply-To: <1224543608.31861.228.camel@brick>
Harvey Harrison wrote:
> __FUNCTION__ is gcc-specific, use __func__
>
> Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
> ---
> These are the last occurences in-tree that are not already coming
> through a subsystem tree.
>
> xtensa, staging and blackfin (serial driver and a fb driver) will
> catch the remaining ones as they merge.
>
> Documentation/DocBook/kernel-hacking.tmpl | 2 +-
> arch/arm/mach-iop13xx/include/mach/time.h | 4 ++--
> arch/arm/mach-pxa/include/mach/zylonite.h | 4 ++--
> arch/powerpc/include/asm/ptrace.h | 2 +-
> drivers/net/usb/pegasus.c | 4 ++--
> 5 files changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/Documentation/DocBook/kernel-hacking.tmpl b/Documentation/DocBook/kernel-hacking.tmpl
> index 4c63e58..ae15d55 100644
> --- a/Documentation/DocBook/kernel-hacking.tmpl
> +++ b/Documentation/DocBook/kernel-hacking.tmpl
> @@ -1105,7 +1105,7 @@ static struct block_device_operations opt_fops = {
> </listitem>
> <listitem>
> <para>
> - Function names as strings (__FUNCTION__).
> + Function names as strings (__func__).
> </para>
> </listitem>
> <listitem>
Ack that part.
Thanks.
prev parent reply other threads:[~2008-10-20 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 23:00 Harvey Harrison
2008-10-20 23:02 ` Randy Dunlap [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=48FD0DEE.7000302@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=harvey.harrison@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=rmk@arm.linux.org.uk \
--cc=torvalds@linux-foundation.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
Powered by JetHome