Write padding in unlink response

[jamesadevine]

As per documentation, an USBIP_CMD_UNLINK response should return 24 bytes of padding.

[coveralls]

Pull Request Test Coverage Report for Build 4114585569

• 0 of 1 (0.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.08%) to 41.641%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/lib.rs	0	1	0.0%

Totals
Change from base Build 4061119800:	-0.08%
Covered Lines:	533
Relevant Lines:	1280

---

💛 - Coveralls

[jiegec]

Wow, the Linux documentation finally provides the structure definition. When I was writing the library, the documentation was so poor that I had to read through linux kernel code.

[jamesadevine]

@jiegec It might be good to review the other calls too based on the documentation. I'm pretty sure there is another case that needs to be handled with USBIP_CMD_UNLINK. See status description below:

[coveralls]

Pull Request Test Coverage Report for Build 4114585569

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 1 (0.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.6%) to 42.365%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/lib.rs	0	1	0.0%

Totals
Change from base Build 4061119800:	0.6%
Covered Lines:	516
Relevant Lines:	1218

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 4114468553

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 1 (0.0%) changed or added relevant line in 1 file are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+0.6%) to 42.33%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/lib.rs	0	1	0.0%

Files with Coverage Reduction	New Missed Lines	%
../../../.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.25.0/src/io/util/write_int.rs	1	72.22%

Totals
Change from base Build 4061119800:	0.6%
Covered Lines:	516
Relevant Lines:	1219

---

💛 - Coveralls