The corresponding syscalls.stp has: probe syscall.inotify_init = kernel.function("sys_inotify_init1").call !, kernel.function("sys_inotify_init").call ?
The reason why it is done this way in syscalls.stp is that in the kernel sys_inotify_init is just a wrapper around sys_inotify_init1. This way we ignore the sys_inotify_init call, and only catch the sys_inotify_init1 call on kernels with sys_inotify_init1. Unfortunately, as bug #11424 notes, '!' (optional and sufficient) doesn't work for kprobe.function probes. So, the above logic will be difficult to duplicate in tapset/nd_syscalls.stp.
Now that bug #11424 and bug #14378 are fixed, this bug can be addressed. Fixed in commit 42f9c99.