crypto: 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> Acked-by:
Daniel P. Berrangé <berrange@redhat.com>
Showing
- crypto/block-luks.c 1 addition, 1 deletioncrypto/block-luks.c
- crypto/block-luks.h 1 addition, 1 deletioncrypto/block-luks.h
- crypto/block-qcow.c 1 addition, 1 deletioncrypto/block-qcow.c
- crypto/block-qcow.h 1 addition, 1 deletioncrypto/block-qcow.h
- crypto/block.c 3 additions, 3 deletionscrypto/block.c
- crypto/cipher.c 3 additions, 3 deletionscrypto/cipher.c
- crypto/ivgen-essiv.c 1 addition, 1 deletioncrypto/ivgen-essiv.c
- crypto/ivgen-essiv.h 1 addition, 1 deletioncrypto/ivgen-essiv.h
- crypto/ivgen-plain.c 1 addition, 1 deletioncrypto/ivgen-plain.c
- crypto/ivgen-plain.h 1 addition, 1 deletioncrypto/ivgen-plain.h
- crypto/ivgen-plain64.c 1 addition, 1 deletioncrypto/ivgen-plain64.c
- crypto/ivgen-plain64.h 1 addition, 1 deletioncrypto/ivgen-plain64.h
- crypto/ivgen.c 4 additions, 4 deletionscrypto/ivgen.c
- crypto/tlscreds.c 1 addition, 1 deletioncrypto/tlscreds.c
- crypto/tlscredsanon.c 1 addition, 1 deletioncrypto/tlscredsanon.c
- crypto/tlscredsx509.c 1 addition, 1 deletioncrypto/tlscredsx509.c
Please register or sign in to comment