Instead of draining additional nodes in each job code, let's do it in
common block_job_drain, draining just all job's children.
It's also a first step to finally get rid of blockjob->blk.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
Hi all!
As a follow-up for "block: drop bs->job" recently
19.06.2019 19:37, Max Reitz wrote:
> On 19.06.19 16:44, Vladimir Sementsov-Ogievskiy wrote:
>> Instead of draining additional nodes in each job code, let's do it in
>> common block_job_drain, draining just all job's children.
>>
>> It's also a first step to finally get rid of blockjob->blk.
>>
>> S
On 19.06.19 16:44, Vladimir Sementsov-Ogievskiy wrote:
> Instead of draining additional nodes in each job code, let's do it in
> common block_job_drain, draining just all job's children.
>
> It's also a first step to finally get rid of blockjob->blk.
>
> Signed-off-by: Vladimir Sementsov-Ogievski
Instead of draining additional nodes in each job code, let's do it in
common block_job_drain, draining just all job's children.
It's also a first step to finally get rid of blockjob->blk.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
Hi all!
As a follow-up for "block: drop bs->job" recently
19.06.2019 17:44, Vladimir Sementsov-Ogievskiy wrote:
> Instead of draining additional nodes in each job code, let's do it in
> common block_job_drain, draining just all job's children.
>
> It's also a first step to finally get rid of blockjob->blk.
Oops, sorry for double-sending.
--
Best regar
Instead of draining additional nodes in each job code, let's do it in
common block_job_drain, draining just all job's children.
It's also a first step to finally get rid of blockjob->blk.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
Hi all!
As a follow-up for "block: drop bs->job" recently
