From: tytso@mit.edu
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: move __func__ into a macro for ext4_warning, ext4_error
Date: Mon, 15 Feb 2010 14:20:07 -0500 [thread overview]
Message-ID: <20100215192007.GA5003@thunk.org> (raw)
In-Reply-To: <4B58AA0C.4040602@redhat.com>
On Thu, Jan 21, 2010 at 09:25:00AM -0000, Eric Sandeen wrote:
> Just a pet peeve of mine; we had a mishash of calls with either __func__
> or "function_name" and the latter tends to get out of sync.
>
> I think it's easier to just hide the __func__ in a macro, and it'll
> be consistent from then on.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Thanks, applied to the ext4 patch queue.
- Ted
prev parent reply other threads:[~2010-02-15 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 19:25 [PATCH] move __func__ into a macro for ext4_warning, ext4_error Eric Sandeen
2010-02-15 19:20 ` tytso [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=20100215192007.GA5003@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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).