Hi David,
>> >+int gdlm_get_lock(lm_lockspace_t *lockspace, struct lm_lockname *name,
>> >+ lm_lock_t **lockp)
>>
>> [lm_lock_t is]
>> currently typedef'ed to void [...]. (One _could_
>> get rid of it, but better not while it is called lm_lock_t. Leave as-is
>> for now.)
>
>I'm wondering what you might suggest instead of using the lm_lockspace_t,
>lm_lock_t, lm_fsdata_t typedefs. These are opaque objects passed between
>gfs and the lock modules. Could you give an example or point to some code
>that shows what you're thinking?
What I was thinking about:
int gdlm_get_lock(void *lockspace, struct lm_lockname *name, void **lockp)
Jan Engelhardt
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
