block: use local path for local headers
When pulling in headers that are in the same directory as the C file (as opposed to one in include/), we should use its relative path, without a directory. Signed-off-by:Michael S. Tsirkin <mst@redhat.com> Reviewed-by:
Philippe Mathieu-Daudé <f4bug@amsat.org> Tested-by:
Philippe Mathieu-Daudé <f4bug@amsat.org>
Showing
- block/crypto.c 1 addition, 1 deletionblock/crypto.c
- block/nbd.c 1 addition, 1 deletionblock/nbd.c
- block/qcow.c 1 addition, 1 deletionblock/qcow.c
- block/qcow2-bitmap.c 1 addition, 1 deletionblock/qcow2-bitmap.c
- block/qcow2-cluster.c 1 addition, 1 deletionblock/qcow2-cluster.c
- block/qcow2-refcount.c 1 addition, 1 deletionblock/qcow2-refcount.c
- block/qcow2-snapshot.c 1 addition, 1 deletionblock/qcow2-snapshot.c
- block/qcow2.c 2 additions, 2 deletionsblock/qcow2.c
- block/vhdx-endian.c 1 addition, 1 deletionblock/vhdx-endian.c
- block/vhdx-log.c 1 addition, 1 deletionblock/vhdx-log.c
- block/vhdx.c 1 addition, 1 deletionblock/vhdx.c
Loading
Please register or sign in to comment