[fuse-discuss] Are all changes of the kernel module done?

[pingxiayu]

Thanks for your help! By patches problem, I meant
http://cr.grommit.com/~mbp/fusefs_type_checking/webrev/:
Workspace: 	/home/mp153739/fuse/fresh/patches/fusefs_type-checking (at 
e0041f2296a4)
Compare against: 	ssh://anon@hg.opensolaris.org/hg/fuse/fusefs (at 
65b662ed5440)

http://cr.grommit.com/~mbp/fusefs_mapin/webrev/:
Workspace: 	/home/mp153739/fuse/fresh/patches/fusefs_mapin (at 
4b9a27cc8898)
Compare against: 	/home/mp153739/fuse/fresh/patches/fusefs_type-checking 
(at e0041f2296a4)

http://cr.grommit.com/~mbp/fusefs_statvfs/webrev/:
Workspace: 	/home/mp153739/fuse/fresh/patches/fusefs_statvfs (at 
ef52755672c3)
Compare against: 	/home/mp153739/fuse/fresh/patches/fusefs_mapin (at 
4b9a27cc8898)

http://cr.grommit.com/~mbp/fusefs_cleanups/webrev/:
Workspace: 	/home/mp153739/fuse/fresh/patches/4-fusefs_cleanups (at 
bf45d04a0f21)
Compare against: 	/home/mp153739/fuse/fresh/patches/3-fusefs_statvfs (at 
6eddef441c9f)

Isn't the forth one supposed to compare against 
/home/mp153739/fuse/fresh/patches/fusefs_statvfs
(at ef52755672c3) rather than against 
/home/mp153739/fuse/fresh/patches/3-fusefs_statvfs (at 6eddef441c9f), if 
it is the forth patch after the third patch?
If the working libfuse comes out, please let us know, OK? Because we are 
really looking forward  to it :)
Thanks for the reply again!
Regards,
XiayuPing

Mark Phalan wrote:
> This patch is to allow fuse to build on Nevada builds after build 62 -
> you'll need at least build 62 to build the fuse module with this patch.
>   
> Really? The patches should be cumulative. The third patch adds
> fuse_statvfs() the fourth definitely includes that functionality... it's
> possible I generated a bad patch. Can you send me more detail on this?
>   
> You could always use GNU patch (gpatch(1)) on Solaris if you are having
> problems with patch(1) - it should be almost identical to whats on
> linux.
>
> By the way, these patches are not enough to get a working libfuse. A
> working libfuse is coming... soon :)
>
> -Mark
>