From 4070ec794ffe3100d7aaa821b709328af49ffc6e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20Kr=C3=B6ning?= Date: Fri, 26 Jul 2024 10:45:59 +0200 Subject: [PATCH] fix(uhyve-interface): clippy::doc_lazy_continuation MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Martin Kröning --- uhyve-interface/src/lib.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/uhyve-interface/src/lib.rs b/uhyve-interface/src/lib.rs index 8a38b780..be833362 100644 --- a/uhyve-interface/src/lib.rs +++ b/uhyve-interface/src/lib.rs @@ -3,8 +3,8 @@ //! The Uhyve hypercall interface works as follows: //! //! - On `x86_64` you use an out port instruction. The address of the `out`-port corresponds to the -//! hypercall you want to use. You can obtain it from the [`IoPorts`] enum. The data send to -//! that port is the physical memory address (of the VM) of the parameters of that hypercall. +//! hypercall you want to use. You can obtain it from the [`IoPorts`] enum. The data send to +//! that port is the physical memory address (of the VM) of the parameters of that hypercall. //! - On `aarch64` you write to the respective [`HypercallAddress`]. The 64-bit value written to that location is the guest's physical memory address of the hypercall's parameter. #![cfg_attr(not(feature = "std"), no_std)]