On Sat, Dec 31, 2022 at 11:31:21PM +0100, Ingo Schwarze wrote:
> Hi Scott,
>
> in the NAME section, please put timeout_add_nsec after timeout_add_usec
> to agree with the order in the SYNOPSIS.
Whoops, done.
> In any case, please go ahead. It appears jmc@ is developing a sore
> elbow from more
Hi Scott,
in the NAME section, please put timeout_add_nsec after timeout_add_usec
to agree with the order in the SYNOPSIS.
In any case, please go ahead. It appears jmc@ is developing a sore
elbow from more than a year of medicine ball ping pong. ;-)
The following are merely suggestions / obser
Thanks! ok mvs@
> On 31 Dec 2022, at 19:22, Scott Cheloha wrote:
>
> mvs@ is nudging me to realign the timeout.9 page with the state of the
> kernel.
>
> Here is my rewrite (again).
>
> There are some bits that I want to rework. The opening paragraph is
> especially clickety-clackety.
>
> St
On Sat, Dec 31, 2022 at 11:22:22AM -0500, Scott Cheloha wrote:
> mvs@ is nudging me to realign the timeout.9 page with the state of the
> kernel.
>
> Here is my rewrite (again).
>
i'm losing track of what i'm reviewing! maybe just put it in and we can
adjust it as needed, if needed.
ok jmc
mvs@ is nudging me to realign the timeout.9 page with the state of the
kernel.
Here is my rewrite (again).
There are some bits that I want to rework. The opening paragraph is
especially clickety-clackety.
Still, I think this is an improvement over what's in-tree. And the
technical content shou
