All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Wang, Wenchao" <wenchao.wang@intel.com>
Cc: Thomas Huth <thuth@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	 Stefan Hajnoczi <stefanha@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	 Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [PATCH] target/i386/hax: Add XCR0 support
Date: Thu, 15 Dec 2022 10:26:42 +0000	[thread overview]
Message-ID: <CAFEAcA-kdF64fzX8Qx4NHstqaTVpqufmiRmCio5V33Lv_xWBBA@mail.gmail.com> (raw)
In-Reply-To: <DM6PR11MB40908AA444148E892A0F8B0D87E19@DM6PR11MB4090.namprd11.prod.outlook.com>

On Thu, 15 Dec 2022 at 09:45, Wang, Wenchao <wenchao.wang@intel.com> wrote:
>
> Hi, Thomas,
>
> Thanks for your reply. I have attempted to follow you suggestions but it always failed on tagging a GPG-signed tag before submitting the pull request. I have used GPG 2.2.4 to generate a RSA4096 GPG secret key and pasted the public key on GitHub successfully.
>
> $ git tag -s pull-request-hax -m 'target/i386/hax: Add XCR0 support'
> error: gpg failed to sign the data
> error: unable to sign the tag
>
> Meanwhile, could @Paolo Bonzini or @Stefan Hajnoczi help to pick the patch up as there is only one-line change for HAX and we have verified it for all guest launching? Thanks a lot.

Yes, please. For a single trivial patch I strongly prefer
that some existing (in this case x86) maintainer takes it in
their pullreq, rather than my having to deal with a
pullreq submission from a new-to-the-process person.
(It's extra work to check submissions from new people,
which is fine if they're going to be doing them a lot
in future, but for a one-off it's a waste of their time
and mine.)

thanks
-- PMM


  reply	other threads:[~2022-12-15 10:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14  9:15 [PATCH] target/i386/hax: Add XCR0 support Wang, Wenchao
2022-12-14  9:39 ` Thomas Huth
2022-12-15  9:45   ` Wang, Wenchao
2022-12-15 10:26     ` Peter Maydell [this message]
2022-12-16  8:47       ` Wang, Wenchao
  -- strict thread matches above, loose matches on Subject: below --
2022-11-25 12:18 Wang, Wenchao
2022-11-25 13:37 ` Philippe Mathieu-Daudé
2022-11-28  8:10   ` Wang, Wenchao
2022-12-27 15:13     ` Paolo Bonzini
2022-12-28  2:55       ` Wang, Wenchao
2022-12-28  8:23         ` Paolo Bonzini
2022-12-28  8:54           ` Wang, Wenchao
2023-01-10  9:30           ` Wang, Wenchao
2022-12-28  3:28       ` Wang, Wenchao
2022-12-05  8:35   ` Wang, Wenchao
2022-12-05  9:05     ` Philippe Mathieu-Daudé
2022-12-05  9:10       ` Wang, Wenchao
2022-12-08  8:22       ` Wang, Wenchao
2022-12-19  9:01       ` Wang, Wenchao
2022-12-19  9:09         ` Philippe Mathieu-Daudé
2022-12-19  9:19           ` Wang, Wenchao
2022-12-27  9:15           ` Wang, Wenchao

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=CAFEAcA-kdF64fzX8Qx4NHstqaTVpqufmiRmCio5V33Lv_xWBBA@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.com \
    --cc=wenchao.wang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.