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: qemu-devel@nongnu.org, contact@canokeys.org,
	MkfsSion <myychina28759@gmail.com>
Subject: Re: [PATCH v2 0/3] CanoKey: Fix xHCI compatibility and CCID ZLP
Date: Sat, 2 Jul 2022 18:58:02 +0800	[thread overview]
Message-ID: <YsAkulsWj5bH7wrT@Sun> (raw)
In-Reply-To: <20220701105106.fzlu44cgvfmb5z4g@sirius.home.kraxel.org>

On Fri, Jul 01, 2022 at 12:51:06PM +0200, Gerd Hoffmann wrote:
> On Thu, Jun 23, 2022 at 11:16:39PM +0800, Hongren (Zenithal) Zheng wrote:
> > On Mon, Jun 13, 2022 at 08:12:38PM +0800, Hongren (Zenithal) Zheng wrote:
> >  
> > > ---
> > > v2: 
> > >   * use usb_ep_get instead of recording ep_in_pointer
> > >       as suggested by kraxel
> > >   * CI result for v2 is at
> > > https://gitlab.com/ZenithalHourlyRate/qemu/-/pipelines/562306905
> > 
> > Hi kraxel, is there any further feedback on this?
> > 
> > BTW, as the commit "add myself as CanoKey maintainer" has been
> > merged, how should I submit patches on CanoKey to you and QEMU?
> 
> Sending to the list with /me Cc'ed is fine.
> 
> > For other contributors, before I can send PULL (my key is not signed yet)
> > I think I should first give Reviewed-by tags then request you
> > to pass them.
> 
> Yes.
> 
> Series queued up now.

Thanks!

> Also I want to add CanoKey in ChangeLog/7.1 in QEMU wiki.
> But the account for wiki should be created by some other
> people with existing accounts. I wonder if you or anyone
> on the list could kindly do me a favor? Thanks!
> 
> My preferred username is Zenithal.

Could you please also add a wiki account for me?

There are two additional patches reviewed by me, and you have been Cc'ed.
I wonder if you could queue them up.

[PATCH v4 1/2] hw: canokey: Remove HS support as not compliant to the spec
[PATCH v4] docs/system/devices/canokey: Document limitations on usb-ehci

> 
> thanks,
>   Gerd
> 


      reply	other threads:[~2022-07-02 11:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 12:12 [PATCH v2 0/3] CanoKey: Fix xHCI compatibility and CCID ZLP Hongren (Zenithal) Zheng
2022-06-13 12:14 ` [PATCH v2 1/3] hw/usb/canokey: Fix " Hongren (Zenithal) Zheng
2022-06-13 12:15 ` [PATCH v2 2/3] hw/usb/canokey: fix compatibility of qemu-xhci Hongren (Zenithal) Zheng
2022-06-13 12:15 ` [PATCH v2 3/3] docs/system/devices/usb/canokey: remove limitations on qemu-xhci Hongren (Zenithal) Zheng
2022-06-23 15:16 ` [PATCH v2 0/3] CanoKey: Fix xHCI compatibility and CCID ZLP Hongren (Zenithal) Zheng
2022-06-23 16:21   ` Hongren (Zenithal) Zheng
2022-07-01 10:51   ` Gerd Hoffmann
2022-07-02 10:58     ` Hongren (Zenithal) Zheng [this message]

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=YsAkulsWj5bH7wrT@Sun \
    --to=i@zenithal.me \
    --cc=contact@canokeys.org \
    --cc=kraxel@redhat.com \
    --cc=myychina28759@gmail.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).