Re: linux-next: Tree for May 20 (ceph)
From: Randy Dunlap
Date: Thu May 20 2010 - 15:53:10 EST
On Thu, 20 May 2010 16:30:42 +1000 Stephen Rothwell wrote:
> Hi all,
>
> We are in the merge window again. I remind you all not to add stuff for
> 2.6.36 to your linux-next trees until after 2.6.35-rc1.
when CONFIG_BLOCK is not enabled:
fs/ceph/messenger.c:732: error: dereferencing pointer to incomplete type
fs/ceph/messenger.c:740: error: dereferencing pointer to incomplete type
fs/ceph/messenger.c:740: error: dereferencing pointer to incomplete type
fs/ceph/messenger.c:740: error: dereferencing pointer to incomplete type
fs/ceph/messenger.c:743: error: dereferencing pointer to incomplete type
fs/ceph/messenger.c:744: error: dereferencing pointer to incomplete type
fs/ceph/messenger.c:793: error: implicit declaration of function 'bio_iovec_idx'
fs/ceph/messenger.c:793: warning : assignment makes pointer from integer without a cast
fs/ceph/messenger.c:794: error: dereferencing pointer to incomplete type
fs/ceph/messenger.c:795: error: dereferencing pointer to incomplete type
fs/ceph/messenger.c:798: error: dereferencing pointer to incomplete type
fs/ceph/messenger.c:1406: warning: initialization makes pointer from integer without a cast
fs/ceph/messenger.c:1413: error: dereferencing pointer to incomplete type
fs/ceph/messenger.c:1413: warning: type defaults to 'int' in declaration of '_min2'
fs/ceph/messenger.c:1413: error: dereferencing pointer to incomplete type
fs/ceph/messenger.c:1416: error: dereferencing pointer to incomplete type
fs/ceph/messenger.c:1416: error: dereferencing pointer to incomplete type
fs/ceph/messenger.c:1424: error: dereferencing pointer to incomplete type
fs/ceph/messenger.c:1429: error: dereferencing pointer to incomplete type
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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/