Fix stray "no" in configure output

[behlendorf]

Motivation and Context

We don't want any extra incorrect noise in the configure output.

Description

This is purely a cosmetic fix which removes a stray "no" from the configure output.

How Has This Been Tested?

Before the change:

checking whether inode_owner_or_capable() exists... yes
checking whether super_block uses const struct xattr_handler... yes
no
checking whether xattr_handler->get() wants dentry and inode and flags... no
checking whether xattr_handler->set() wants dentry, inode, and mnt_idmap... no

after

checking whether inode_owner_or_capable() exists... yes
checking whether super_block uses const struct xattr_handler... yes
checking whether xattr_handler->get() wants dentry and inode and flags... no
checking whether xattr_handler->set() wants dentry, inode, and mnt_idmap... no

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Performance enhancement (non-breaking change which improves efficiency)
• Code cleanup (non-breaking change which makes code smaller or more readable)
• Breaking change (fix or feature that would cause existing functionality to change)
• Library ABI change (libzfs, libzfs_core, libnvpair, libuutil and libzfsbootenv)
• Documentation (a change to man pages or other documentation)

Checklist:

• My code follows the OpenZFS code style requirements.
• I have updated the documentation accordingly.
• I have read the contributing document.
• I have added tests to cover my changes.
• I have run the ZFS Test Suite with this change applied.
• All commit messages are properly formatted and contain Signed-off-by.