linux-ext4 - Why the third parameter of "ext4_ext_put_in_cache" is _

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <3d0408630707260754w71df514bh719a6e40cc6e2fdb@mail.gmail.com>
Date:	Thu, 26 Jul 2007 22:54:41 +0800
From:	"Yan Zheng" <yanzheng@...n.com>
To:	linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Why the third parameter of "ext4_ext_put_in_cache" is __u32?

Hi all

  The third parameter of "ext4_ext_put_in_cache" is used to receive
physical block number. I think the data type should be "ext4_fsblk_t".

Thanks in advance.

YZ
-
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