From: Joe Perches <joe@perches.com>
To: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-ide <linux-ide@vger.kernel.org>
Subject: Re: [PATCH 2/3] IDE: Replace __FUNCTION__ with __func__
Date: Sun, 24 Feb 2008 16:04:48 -0800 [thread overview]
Message-ID: <1203897888.19319.143.camel@localhost> (raw)
In-Reply-To: <20080224221113.5ddfe371@paolo-desktop>
On Sun, 2008-02-24 at 22:11 +0100, Paolo Ciarrocchi wrote:
> - "driver.\n", __FUNCTION__, drive->name);
> + "driver.\n", __func__, drive->name);
Is there consensus on this style conversion?
Right now, there's 629 uses of __FUNCTION__ and 439 uses of __func__.
next prev parent reply other threads:[~2008-02-25 0:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 21:11 [PATCH 2/3] IDE: Replace __FUNCTION__ with __func__ Paolo Ciarrocchi
2008-02-25 0:04 ` Joe Perches [this message]
2008-02-25 6:44 ` Paolo Ciarrocchi
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=1203897888.19319.143.camel@localhost \
--to=joe@perches.com \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.ciarrocchi@gmail.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;
as well as URLs for NNTP newsgroup(s).