Re: 2.6.18-rc1-mm1

[Randy.Dunlap]

On Mon, 10 Jul 2006 22:58:50 -0400 Chuck Ebbert wrote:

> On Sun, 9 Jul 2006 02:11:06 -0700, Andrew morton wrote:
> 
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
> 
> Warnings(?) during build:
> 
> /home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/ipconfig' given more than once in the same rule.
> /home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/nfsmount' given more than once in the same rule.
> /home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/run-init' given more than once in the same rule.
> /home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/fstype' given more than once in the same rule.

Yes, and these:

fs/ecryptfs/main.c:327: warning: format â%dâ expects type âintâ, but argument 3 has type âsize_tâ
fs/ecryptfs/crypto.c:1599: warning: format â%dâ expects type âintâ, but argument 2 has type âsize_tâ
fs/ecryptfs/crypto.c:1621: warning: format â%dâ expects type âintâ, but argument 2 has type âsize_tâ
fs/ecryptfs/crypto.c:1628: warning: format â%dâ expects type âintâ, but argument 2 has type âsize_tâ
fs/ecryptfs/crypto.c:1635: warning: format â%dâ expects type âintâ, but argument 2 has type âsize_tâ
fs/ecryptfs/crypto.c:1642: warning: format â%dâ expects type âintâ, but argument 2 has type âsize_tâ
fs/ecryptfs/crypto.c:1649: warning: format â%dâ expects type âintâ, but argument 2 has type âsize_tâ
fs/ecryptfs/crypto.c:1656: warning: format â%dâ expects type âintâ, but argument 2 has type âsize_tâ
drivers/acpi/executer/exmutex.c:268: warning: format â%Xâ expects type âunsigned intâ, but argument 4 has type âstruct task_struct *â
drivers/acpi/executer/exmutex.c:268: warning: format â%Xâ expects type âunsigned intâ, but argument 6 has type âstruct task_struct *â


I'll get to these sometime this week if noone else does.
(not the klibc warnings)

---
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/