mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2025-02-05 18:20:34 +00:00
sys_util: drop redundant empty return type
rustfmt incorrectly formats the `handler` parameter in register_signal_handler in a way that actually breaks compilation. This bug has been reported upstream already, but it is not fixed yet on the version of rustfmt available with stable rust: https://github.com/rust-lang/rustfmt/issues/3673 However, the empty return type can just be omitted in this case, which avoids the rustfmt bug. BUG=None TEST=`bin/fmt --check` passes with Rust 1.36.0 Change-Id: I75c49c66f1db9cb6ae73cc0f6f3e66351176c474 Signed-off-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/1724849 Reviewed-by: Zach Reizner <zachr@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com>
This commit is contained in:
parent
2ea297ac76
commit
fb32e98f86
1 changed files with 1 additions and 4 deletions
|
@ -100,10 +100,7 @@ fn valid_signal_num(num: c_int) -> bool {
|
|||
///
|
||||
/// This is considered unsafe because the given handler will be called asynchronously, interrupting
|
||||
/// whatever the thread was doing and therefore must only do async-signal-safe operations.
|
||||
pub unsafe fn register_signal_handler(
|
||||
num: c_int,
|
||||
handler: extern "C" fn() -> (),
|
||||
) -> errno::Result<()> {
|
||||
pub unsafe fn register_signal_handler(num: c_int, handler: extern "C" fn()) -> errno::Result<()> {
|
||||
if !valid_signal_num(num) {
|
||||
return Err(errno::Error::new(EINVAL));
|
||||
}
|
||||
|
|
Loading…
Reference in a new issue