On 02/03/22 21:25, Eric Blake wrote:
> Recent patches have demonstrated confusion on the order in which
> callbacks are reached, when it is safe or dangerous to ignore *error,
> and what a completion callback should do when auto-retirement is in
> use. Add wording to make it more obvious that:
>
()On Thu, Feb 3, 2022 at 10:28 PM Eric Blake wrote:
>
> Recent patches have demonstrated confusion on the order in which
> callbacks are reached, when it is safe or dangerous to ignore *error,
> and what a completion callback should do when auto-retirement is in
> use. Add wording to make it more
Recent patches have demonstrated confusion on the order in which
callbacks are reached, when it is safe or dangerous to ignore *error,
and what a completion callback should do when auto-retirement is in
use. Add wording to make it more obvious that:
- callbacks are reached in the following order:
