The ioctl_io*_nr macros expand to blocks that again contain macros. However, when doing this, the expanded code did not use $crate, meaning those submacros had to be in-scope at the call site. This could cause surpising compilation failures if macros were not imported, but rather referred to by their full name (e.g.
vmm-sys-utils::ioctls::ioctl_iow_nr!).
Requirements
Before submitting your PR, please make sure you addressed the following
requirements:
[ ] All commits in this PR are signed (with git commit -s), and the commit
message has max 60 characters for the summary and max 75 characters for each
description line.
[ ] All added/changed functionality has a corresponding unit/integration
test.
[ ] All added/changed public-facing functionality has entries in the "Upcoming
Release" section of CHANGELOG.md (if no such section exists, please create one).
[ ] Any newly added unsafe code is properly documented.
Summary of the PR
The
ioctl_io*_nrmacros expand to blocks that again contain macros. However, when doing this, the expanded code did not use$crate, meaning those submacros had to be in-scope at the call site. This could cause surpising compilation failures if macros were not imported, but rather referred to by their full name (e.g.vmm-sys-utils::ioctls::ioctl_iow_nr!).Requirements
Before submitting your PR, please make sure you addressed the following requirements:
git commit -s), and the commit message has max 60 characters for the summary and max 75 characters for each description line.unsafecode is properly documented.