From 84f33b61e938306e87dae1125a13dfbeef9432a0 Mon Sep 17 00:00:00 2001 From: bunnie Date: Thu, 27 Jun 2024 00:22:27 +0800 Subject: [PATCH] we're going to have to bump all the pins because *formatting* Cargo changed how it decided to format some comments in one of our key dependency crates, which is breaking all of our CI checks. This fixes that. *sigh*. --- xous-rs/src/syscall.rs | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/xous-rs/src/syscall.rs b/xous-rs/src/syscall.rs index 0409f4858..acab0fa26 100644 --- a/xous-rs/src/syscall.rs +++ b/xous-rs/src/syscall.rs @@ -418,8 +418,8 @@ pub enum SysCall { /// /// ## Arguments /// - /// * **Index**: The item to adjust. Currently the following limits are supported: 1: Maximum heap size - /// 2: Current heap size + /// * **Index**: The item to adjust. Currently the following limits are supported: 1: Maximum heap size 2: + /// Current heap size /// * **Current Limit**: Pass the current limit value here. The current limit must match in order for the /// new limit to take effect. This is used to avoid a race condition if two threads try to set the same /// limit. @@ -464,8 +464,8 @@ pub enum SysCall { /// /// ## Arguments /// - /// * **MessageSender**: This is the `sender` from the message envelope. It is a unique ID that - /// identifies this message, as well as the server it came from. + /// * **MessageSender**: This is the `sender` from the message envelope. It is a unique ID that identifies + /// this message, as well as the server it came from. /// /// The remaining arguments depend on whether the message was a `BlockingScalar` /// message or a `MemoryMessage`. Note that this function should NOT be called