From: Oleg Drokin <green@namesys.com>
To: Alan Cox <alan@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19-ac4
Date: Tue, 6 Aug 2002 19:46:18 +0400 [thread overview]
Message-ID: <20020806194618.A19899@namesys.com> (raw)
In-Reply-To: <200208051147.g75Blh720012@devserv.devel.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 296 bytes --]
Hello!
On Mon, Aug 05, 2002 at 07:47:43AM -0400, Alan Cox wrote:
> o Fix __FUNCTION__ warnings in reiserfs (me)
I see people reporting this change is not working correctly,
so I think I might as well submit my own implementation that works
and that we plan to push to Marcelo.
Bye,
Oleg
[-- Attachment #2: 683 --]
[-- Type: text/plain, Size: 3412 bytes --]
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet 1.682 -> 1.683
# fs/reiserfs/namei.c 1.20 -> 1.21
# include/linux/reiserfs_fs.h 1.18 -> 1.19
# fs/reiserfs/bitmap.c 1.13 -> 1.14
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 02/08/06 green@angband.namesys.com 1.683
# reiserfs_fs.h, namei.c, bitmap.c:
# fix __FUNCTION__ usage to prevent gcc 3.1+ warnings
# --------------------------------------------
#
diff -Nru a/fs/reiserfs/bitmap.c b/fs/reiserfs/bitmap.c
--- a/fs/reiserfs/bitmap.c Tue Aug 6 10:38:10 2002
+++ b/fs/reiserfs/bitmap.c Tue Aug 6 10:38:10 2002
@@ -683,7 +683,7 @@
{
#ifdef CONFIG_REISERFS_CHECK
if (inode->u.reiserfs_i.i_prealloc_count < 0)
- reiserfs_warning("zam-4001:" __FUNCTION__ ": inode has negative prealloc blocks count.\n");
+ reiserfs_warning("zam-4001:%s: inode has negative prealloc blocks count.\n", __FUNCTION__);
#endif
if (inode->u.reiserfs_i.i_prealloc_count > 0) {
__discard_prealloc(th, inode);
@@ -699,7 +699,7 @@
inode = list_entry(plist->next, struct inode, u.reiserfs_i.i_prealloc_list);
#ifdef CONFIG_REISERFS_CHECK
if (!inode->u.reiserfs_i.i_prealloc_count) {
- reiserfs_warning("zam-4001:" __FUNCTION__ ": inode is in prealloc list but has no preallocated blocks.\n");
+ reiserfs_warning("zam-4001:%s: inode is in prealloc list but has no preallocated blocks.\n", __FUNCTION__);
}
#endif
__discard_prealloc(th, inode);
diff -Nru a/fs/reiserfs/namei.c b/fs/reiserfs/namei.c
--- a/fs/reiserfs/namei.c Tue Aug 6 10:38:10 2002
+++ b/fs/reiserfs/namei.c Tue Aug 6 10:38:10 2002
@@ -287,7 +287,7 @@
while (1) {
retval = search_by_entry_key (dir->i_sb, &key_to_search, path_to_entry, de);
if (retval == IO_ERROR) {
- reiserfs_warning ("zam-7001: io error in " __FUNCTION__ "\n");
+ reiserfs_warning ("zam-7001: io error in %s\n", __FUNCTION__);
return IO_ERROR;
}
@@ -413,8 +413,8 @@
}
if (retval != NAME_FOUND) {
- reiserfs_warning ("zam-7002:" __FUNCTION__ ": \"reiserfs_find_entry\" has returned"
- " unexpected value (%d)\n", retval);
+ reiserfs_warning ("zam-7002:%s: \"reiserfs_find_entry\" has returned"
+ " unexpected value (%d)\n", __FUNCTION__, retval);
}
return -EEXIST;
diff -Nru a/include/linux/reiserfs_fs.h b/include/linux/reiserfs_fs.h
--- a/include/linux/reiserfs_fs.h Tue Aug 6 10:38:10 2002
+++ b/include/linux/reiserfs_fs.h Tue Aug 6 10:38:10 2002
@@ -75,9 +75,9 @@
/** always check a condition and panic if it's false. */
#define RASSERT( cond, format, args... ) \
if( !( cond ) ) \
- reiserfs_panic( 0, "reiserfs[%i]: assertion " #cond " failed at " \
- __FILE__ ":%i:" __FUNCTION__ ": " format "\n", \
- in_interrupt() ? -1 : current -> pid, __LINE__ , ##args )
+ reiserfs_panic( 0, "reiserfs[%i]: assertion " #cond " failed at " \
+ __FILE__ ":%i:%s: " format "\n", \
+ in_interrupt() ? -1 : current -> pid, __LINE__ , __FUNCTION__ , ##args )
#if defined( CONFIG_REISERFS_CHECK )
#define RFALSE( cond, format, args... ) RASSERT( !( cond ), format, ##args )
next prev parent reply other threads:[~2002-08-06 15:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 11:47 Linux 2.4.19-ac4 Alan Cox
2002-08-05 18:10 ` Tomas Szepe
2002-08-05 18:43 ` Tomas Szepe
2002-08-05 19:59 ` Adrian Bunk
2002-08-05 20:00 ` Alan Cox
2002-08-05 20:56 ` James Mayer
2002-08-05 22:19 ` Alan Cox
2002-08-05 22:31 ` Thunder from the hill
2002-08-06 1:58 ` Gary White
2002-08-07 12:22 ` Kasper Dupont
2002-08-05 22:44 ` Adrian Bunk
2002-08-06 12:13 ` [lkml] " Ian Soboroff
2002-08-06 12:30 ` Ian Soboroff
2002-08-07 14:31 ` Alan Cox
2002-08-12 12:12 ` Ian Soboroff
2002-08-06 15:46 ` Oleg Drokin [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-05 17:46 Jean Tourrilhes
2002-08-05 20:31 ` Alan Cox
2002-08-05 20:04 ` Jean Tourrilhes
2002-08-05 21:35 ` Alan Cox
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=20020806194618.A19899@namesys.com \
--to=green@namesys.com \
--cc=alan@redhat.com \
--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