qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Hongren (Zenithal) Zheng" <i@zenithal.me>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
	qemu-devel@nongnu.org, contact@canokeys.org
Subject: Re: [PATCH v4 0/6] Introduce CanoKey QEMU
Date: Tue, 22 Mar 2022 15:18:02 +0800	[thread overview]
Message-ID: <Yjl4KqzeVBjNL1z0@Sun> (raw)
In-Reply-To: <20220304105119.wcmgrlefsawnqmc2@sirius.home.kraxel.org>

On Fri, Mar 04, 2022 at 11:51:19AM +0100, Gerd Hoffmann wrote:
> On Sat, Feb 12, 2022 at 09:29:47PM +0800, Hongren (Zenithal) Zheng wrote:
> > Hi,
> > 
> > Is there any further feedback on this patch set.
> 
> Sorry for the looong delay, I'm rather busy with edk2.

Fully understandable. There is also delay on my side, sorry for that
too.

> 
> Tried to queue up this, noticed it breaks the build in case the
> canokey library is not installed.

Yes, this is my fault. I forgot to put `softmmu_ss.add(canokey)`
inside a `if canokey.found()` conditional check.

I've fixed it with 
https://gitlab.com/ZenithalHourlyRate/qemu/-/commit/5d8604c70abefc8146dbb4f7836f3215bc9df966
which will be contained in v5.

> 
> I'd suggest to run the patch series through the qemu gitlab CI
> before sending out v5.

I have gone through qemu gitlab CI and the result is in
https://gitlab.com/ZenithalHourlyRate/qemu/-/pipelines/497317417
Except check-dco and check-patch (I only generate Signed-off-by line
when `git format-patch`), other failed checks are "allowed to fail" and
I've checked the log, these failures are about Debian RISC-V packages
instead of qemu itself.

Is this appropriate for sending out v5?

By the way, we are planning to separate libcanokey-qemu.so
from canokey-core to a dedicated repo at
https://github.com/canokeys/canokey-qemu
(not done yet), which would result in changes in documentation.
I will contain these changes in v5 once we are done.

> 
> take care,
>   Gerd
> 

Regards,

Hongren


  reply	other threads:[~2022-03-22  7:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27  9:41 [PATCH v4 0/6] Introduce CanoKey QEMU Hongren (Zenithal) Zheng
2022-01-27  9:45 ` [PATCH v4 1/6] hw/usb: Add CanoKey Implementation Hongren (Zenithal) Zheng
2022-01-27  9:46 ` [PATCH v4 2/6] hw/usb/canokey: Add trace events Hongren (Zenithal) Zheng
2022-01-27  9:46 ` [PATCH v4 3/6] meson: Add CanoKey Hongren (Zenithal) Zheng
2022-01-27  9:47 ` [PATCH v4 4/6] docs: Add CanoKey documentation Hongren (Zenithal) Zheng
2022-01-27  9:47 ` [PATCH v4 5/6] docs/system/devices/usb: Add CanoKey to USB devices examples Hongren (Zenithal) Zheng
2022-01-27  9:47 ` [PATCH v4 6/6] MAINTAINERS: add myself as CanoKey maintainer Hongren (Zenithal) Zheng
2022-02-12 13:29 ` [PATCH v4 0/6] Introduce CanoKey QEMU Hongren (Zenithal) Zheng
2022-03-04 10:51   ` Gerd Hoffmann
2022-03-22  7:18     ` Hongren (Zenithal) Zheng [this message]
2022-03-22 10:41       ` Gerd Hoffmann

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=Yjl4KqzeVBjNL1z0@Sun \
    --to=i@zenithal.me \
    --cc=contact@canokeys.org \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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).