sanatize kdev_t?

David J. M. Karlsen (david@davidkarlsen.com)
Wed, 18 Sep 2002 01:16:18 +0200


lvm.c:1: #error Broken until maintainers will sanitize kdev_t handling
lvm.c:381: unknown field `sizes' specified in initializer
lvm.c:381: warning: initialization from incompatible pointer type
lvm.c:382: unknown field `nr_real' specified in initializer
lvm.c:382: warning: initialization makes pointer from integer without a cast
lvm.c: In function `lvm_user_bmap':
lvm.c:1010: structure has no member named `bi_dev'
lvm.c:1011: structure has no member named `bi_dev'
lvm.c:1019: structure has no member named `bi_dev'
lvm.c:1019: structure has no member named `bi_dev'
lvm.c:1019: structure has no member named `bi_dev'
lvm.c:1019: structure has no member named `bi_dev'
lvm.c: In function `lvm_map':
lvm.c:1089: structure has no member named `bi_dev'
lvm.c:1213: structure has no member named `bi_dev'
lvm.c: In function `lvm_do_pe_lock_unlock':
lvm.c:1319: warning: implicit declaration of function `fsync_dev'
lvm.c: In function `__update_hardsectsize':
lvm.c:1787: warning: implicit declaration of function `get_hardsect_size'
lvm.c: In function `lvm_do_lv_remove':
lvm.c:2125: warning: implicit declaration of function `invalidate_buffers'
lvm.c: In function `lvm_geninit':
lvm.c:2658: `blksize_size' undeclared (first use in this function)
lvm.c:2658: (Each undeclared identifier is reported only once
lvm.c:2658: for each function it appears in.)
make[3]: *** [lvm.o] Error 1
make[3]: Leaving directory `/tmp/linux-2.5.35/drivers/md'
make[2]: *** [md] Error 2
make[2]: Leaving directory `/tmp/linux-2.5.35/drivers'
make[1]: *** [drivers] Error 2
make[1]: Leaving directory `/tmp/linux-2.5.35'
make: *** [stamp-build] Error 2

so - is sanatizing far away? whats changed - and why. I'd love to
experiment a little with 2.5.x - but I really need the md and lvm stuff.

-- 
David J. M. Karlsen
http://www.davidkarlsen.com - http://mp3.davidkarlsen.com
+47 90 68 22 43

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