linux-ext4 - [PATCH] ext4: fix the code style from printk to ext

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CADxeRwnv7quZbWn9xZ=KnEg_KyT65DApEt57zDdgeYsRgQKYQw@mail.gmail.com>
Date:	Sat, 12 May 2012 23:57:13 +0800
From:	Steven Liu <lingjiujianke@...il.com>
To:	linux-ext4@...r.kernel.org
Cc:	tytso@....edu, linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	linux-kernel@...r.kernel.org
Subject: [PATCH] ext4: fix the code style from printk to ext_debug in extents.c

Hi Ted,

just fix the printk debug to ext_debug, if undefined the EXT_DEBUG
it will not output the debug message

Signed-off-by: LiuQi <liuqi@...loud.cn>
---
 fs/ext4/extents.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
index abcdeab..211e230 100644
--- a/fs/ext4/extents.c
+++ b/fs/ext4/extents.c
@@ -548,10 +548,10 @@ ext4_ext_binsearch_idx(struct inode *inode,
        for (k = 0; k < le16_to_cpu(eh->eh_entries); k++, ix++) {
          if (k != 0 &&
              le32_to_cpu(ix->ei_block) <= le32_to_cpu(ix[-1].ei_block)) {
-               printk(KERN_DEBUG "k=%d, ix=0x%p, "
+               ext_debug("k=%d, ix=0x%p, "
                       "first=0x%p\n", k,
                       ix, EXT_FIRST_INDEX(eh));
-               printk(KERN_DEBUG "%u <= %u\n",
+               ext_debug("%u <= %u\n",
                       le32_to_cpu(ix->ei_block),
                       le32_to_cpu(ix[-1].ei_block));
            }
--
1.7.1



Best Regards
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html