-
Notifications
You must be signed in to change notification settings - Fork 207
doc/ipc: copyedits #278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc/ipc: copyedits #278
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello! Thanks for fixing some stuff! I'm going to merge 2/3 of this. Comments below.
@@ -272,7 +272,7 @@ A concrete mapping of these operations to IPCs might go as follows. | |||
|
|||
- Message is a four-byte struct containing `fd` as a little-endian `u32`. Borrow | |||
0 is `buffer` and must be writable. | |||
- Data will be written to a prefix of borrow 0, starting at offset 0. | |||
- Data will be written to a prefix of lease 0, starting at offset 0. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Both are technically correct here, since "borrow" is the term used at the server side, while "lease" is from the client's perspective. I'm happy to accept this change though since this section is a little informal, and the old usage clearly surprised you.
@@ -309,7 +309,7 @@ fn read(task: TaskId, fd: u32, buffer: &mut [u8]) -> Result<usize, IoError> { | |||
let (rc, len) = sys_send( | |||
task, | |||
0, | |||
&u32.to_le_bytes(), | |||
&fd.to_le_bytes(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Heh, nice.
doc/timers.adoc
Outdated
@@ -35,7 +35,7 @@ Each task gets a timer. The timer has three properties: | |||
- A _notification set._ | |||
|
|||
At periodic intervals (ticks), if the enable bit is set, the kernel checks the | |||
deadline to see if it is in the future. If not (it is `<=` the current time), | |||
deadline to see if it is in the future. If not (it is \<=; the current time), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry to round trip this again, but, \<=;
produces <=;
in the HTML output -- this needs to be just \<=
without the semicolon.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whoops. Done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You might want to keep the backticks here.
See this example: https://gist.github.com/fernandogmo/34032124e94c6b383277decd8631c687
The protocol uses leases, the Rust code uses borrows.