From: "Hongren (Zenithal) Zheng" <i@zenithal.me>
To: Gerd Hoffmann <kraxel@redhat.com>, "Canokeys.org" <contact@canokeys.org>
Cc: qemu-devel@nongnu.org, tlaurion <insurgo@riseup.net>
Subject: [PATCH 0/2] canokey: documentation fixes
Date: Mon, 12 Jun 2023 16:36:02 +0800 [thread overview]
Message-ID: <ZIbY8nBXQbv2qZJ8@Sun> (raw)
This patch series updates the documentation for
canokey in QEMU.
Kraxel, could you please pass these patches?
I still do not get my gpg key signed.
Hopefully I could meet some QEMU maintainers soon
and then I can send a PULL.
The following patch also needs to be passed.
https://lore.kernel.org/qemu-devel/ZE5z+2WbvVpTa82H@Sun/
Thanks,
Hongren (Zenithal) Zheng (2):
docs/system/devices/canokey: fix recursive cloning
docs/system/devices/canokey: update implementations and web console
docs/system/devices/canokey.rst | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
--
2.37.2
next reply other threads:[~2023-06-12 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 8:36 Hongren (Zenithal) Zheng [this message]
2023-06-12 8:42 ` [PATCH 1/2] docs/system/devices/canokey: fix recursive cloning Hongren (Zenithal) Zheng
2023-06-12 8:44 ` [PATCH 2/2] docs/system/devices/canokey: update implementations and web console Hongren (Zenithal) Zheng
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=ZIbY8nBXQbv2qZJ8@Sun \
--to=i@zenithal.me \
--cc=contact@canokeys.org \
--cc=insurgo@riseup.net \
--cc=kraxel@redhat.com \
--cc=qemu-devel@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;
as well as URLs for NNTP newsgroup(s).