misc: Adapt consistent import style formatting

Historically the Cloud Hypervisor coding style has been to ensure that
all imports are ordered and placed in a single group. Unfortunately
cargo fmt has no support for ensuring that all imports are in a single
group so if whitespace lines were added as part of the import statements
then they would only be odered correctly in the group.

By adopting "group_imports="StdExternalCrate" we can enforce a style
where imports are placed in at most three groups for std, external
crates and the crate itself. Choosing a style enforceable by the tooling
reduces the reviewer burden.

Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
This commit is contained in:
Rob Bradford 2024-09-29 10:48:45 +01:00
parent 6e4aefe66f
commit 88a9f79944
153 changed files with 1185 additions and 924 deletions

View file

@ -5,9 +5,6 @@
#![allow(clippy::undocumented_unsafe_blocks)]
use once_cell::sync::Lazy;
use serde_json::Value;
use ssh2::Session;
use std::env;
use std::ffi::OsStr;
use std::fmt::Display;
@ -24,6 +21,10 @@ use std::sync::Mutex;
use std::thread;
use std::time::Duration;
use std::{fmt, fs};
use once_cell::sync::Lazy;
use serde_json::Value;
use ssh2::Session;
use vmm_sys_util::tempdir::TempDir;
use wait_timeout::ChildExt;