On 05/25/2018 01:47 PM, Michael S. Tsirkin wrote:
> When pulling in headers that are in the same directory as C file (as
> opposed to one in include/), we should use its relative path, without a
> directory.
>
> Signed-off-by: Michael S. Tsirkin
Reviewed-by: Philippe Mathieu-Daudé
Tested-by: Ph
On 05/25/2018 11:47 AM, Michael S. Tsirkin wrote:
When pulling in headers that are in the same directory as C file (as
s/as C/as the C/
opposed to one in include/), we should use its relative path, without a
directory.
Signed-off-by: Michael S. Tsirkin
---
block/crypto.c | 2 +-
When pulling in headers that are in the same directory as C file (as
opposed to one in include/), we should use its relative path, without a
directory.
Signed-off-by: Michael S. Tsirkin
---
block/crypto.c | 2 +-
block/nbd.c| 2 +-
block/qcow.c | 2 +-
block/qcow2-b
