On 7/6/22 23:15, Emanuele Giuseppe Esposito wrote:
This comment applies more on job, it was left in blockjob as in the past
the whole job logic was implemented there.

Note: at this stage, job_{lock/unlock} and job lock guard macros
are*nop*.

No functional change intended.

Signed-off-by: Emanuele Giuseppe Esposito<eespo...@redhat.com>

Reviewed-by: Vladimir Sementsov-Ogievskiy <vsement...@yandex-team.ru>

--
Best regards,
Vladimir

Reply via email to