On Wed, Jan 15, 2014 at 05:31:56PM +0000, Taylor R Campbell wrote: > As is, existing code calling, e.g., VOP_MKDIR will still compile. Is > there a reason the versioning doesn't rename it to VOP_MKDIR_V2? > > For that matter, why new machinery for this versioning stuff at all? > Why not just rename the vop from mkdir to mkdir_v2? That would take > care of both struct vop_mkdir_v2_args and VOP_MKDIR_V2. Am I missing > something?
Well, one thing is that there aren't expected to be out-of-tree callers of VOP_MKDIR, only out-of-tree callees. It is convenient to be able to break callers too, but I'm ok with doing it some other way temporarily while hacking. -- David A. Holland dholl...@netbsd.org