Changyuan Lyu <changyuanl@xxxxxxxxxx> writes: > ``ENOTTY` -> ``ENOTTY``. > > Signed-off-by: Changyuan Lyu <changyuanl@xxxxxxxxxx> > --- > Documentation/virt/kvm/x86/amd-memory-encryption.rst | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/virt/kvm/x86/amd-memory-encryption.rst b/Documentation/virt/kvm/x86/amd-memory-encryption.rst > index 487b6328b3e7..995780088eb2 100644 > --- a/Documentation/virt/kvm/x86/amd-memory-encryption.rst > +++ b/Documentation/virt/kvm/x86/amd-memory-encryption.rst > @@ -57,7 +57,7 @@ information, see the SEV Key Management spec [api-spec]_ > > The main ioctl to access SEV is KVM_MEMORY_ENCRYPT_OP. If the argument > to KVM_MEMORY_ENCRYPT_OP is NULL, the ioctl returns 0 if SEV is enabled > -and ``ENOTTY` if it is disabled (on some older versions of Linux, > +and ``ENOTTY`` if it is disabled (on some older versions of Linux, > the ioctl runs normally even with a NULL argument, and therefore will Applied, thanks. jon
