From: Michael Tokarev <mjt@tls.msk.ru>
To: qemu-devel@nongnu.org
Cc: Stefan Weil via <qemu-trivial@nongnu.org>,
Michael Tokarev <mjt@tls.msk.ru>
Subject: [PULL 2/4] Fix include statement for u2f-emu.h
Date: Mon, 23 Mar 2026 16:00:14 +0300 [thread overview]
Message-ID: <20260323130021.376393-3-mjt@tls.msk.ru> (raw)
In-Reply-To: <20260323130021.376393-1-mjt@tls.msk.ru>
From: Stefan Weil via <qemu-trivial@nongnu.org>
All examples on https://github.com/Agnoctopus/libu2f-emu/ don't
simply include u2f-emu.h without any added directory.
The additional include directory does not exist when libu2f
was built with meson.
It's up to pkgconfig to make sure that u2f-emu.h is found in any case.
Signed-off-by: Stefan Weil <sw@weilnetz.de>
Reviewed-by: Michael Tokarev <mjt@tls.msk.ru>
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
---
hw/usb/u2f-emulated.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/usb/u2f-emulated.c b/hw/usb/u2f-emulated.c
index 196d05a83a..b82a315019 100644
--- a/hw/usb/u2f-emulated.c
+++ b/hw/usb/u2f-emulated.c
@@ -31,7 +31,7 @@
#include "hw/usb/usb.h"
#include "hw/core/qdev-properties.h"
-#include <u2f-emu/u2f-emu.h>
+#include <u2f-emu.h>
#include "u2f.h"
--
2.47.3
next prev parent reply other threads:[~2026-03-23 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 13:00 [PULL 0/4] Trivial patches for 2026-03-23 Michael Tokarev
2026-03-23 13:00 ` [PULL 1/4] tests: fix typo in char unit test comment Michael Tokarev
2026-03-23 13:00 ` Michael Tokarev [this message]
2026-03-23 13:00 ` [PULL 3/4] docs: Update GitHub URL of libu2f-emu Michael Tokarev
2026-03-23 13:00 ` [PULL 4/4] Fix several typos in documentation (found by codespell) Michael Tokarev
2026-03-23 16:49 ` [PULL 0/4] Trivial patches for 2026-03-23 Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260323130021.376393-3-mjt@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox