All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sunil Muthuswamy <sunilmut@microsoft.com>
To: Paolo Bonzini <bonzini@gnu.org>,
	Richard Henderson <rth@twiddle.net>,
	Eduardo Habkost <ehabkost@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Stefan Weil <sw@weilnetz.de>
Subject: RE: [EXTERNAL] Re: PATCH] WHPX: TSC get and set should be dependent on VM state
Date: Tue, 14 Jul 2020 18:13:30 +0000	[thread overview]
Message-ID: <SN4PR2101MB0880D99F3629960AFDB4ABC6C0610@SN4PR2101MB0880.namprd21.prod.outlook.com> (raw)
In-Reply-To: <da716e14-0716-93a1-bbb2-da25fca0d47b@gnu.org>

> >
> > Thanks. Ok, I am setup with GPG. Where should I be sending the pull requests to? Who is "Peter"? Do I have to send it to you?
> 
> Peter is Peter Maydell, but for now you can send them to me.  I'll get
> round to documenting the remaining steps.
> 
> Unfortunately all the scripts I have for this use the Unix shell, but
> they are just a few lines so I might try to rewrite them in Python.
> This way you can use them from Windows without needing to bring up WSL
> or anything like that.
> 
> Paolo

Paolo, just wanted to make sure that I understood your request. You are asking
me to submit my WHPX changes as signed PRs. But, are you also asking that I
maintain a QEMU fork for all WHPX changes (as WHPX maintainer) and merge
those occasionally? Or, should the other WHPX changes from others be submitted
directly upstream?

      reply	other threads:[~2020-07-14 18:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-26 20:54 PATCH] WHPX: TSC get and set should be dependent on VM state Sunil Muthuswamy
2020-02-28 10:45 ` Paolo Bonzini
2020-02-28 21:02   ` [EXTERNAL] " Sunil Muthuswamy
2020-02-29  9:39     ` Paolo Bonzini
2020-03-02 19:59       ` Sunil Muthuswamy
2020-03-03 17:52         ` Paolo Bonzini
2020-03-04 22:44           ` Sunil Muthuswamy
2020-03-04 22:47             ` Paolo Bonzini
2020-07-14 18:13               ` Sunil Muthuswamy [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=SN4PR2101MB0880D99F3629960AFDB4ABC6C0610@SN4PR2101MB0880.namprd21.prod.outlook.com \
    --to=sunilmut@microsoft.com \
    --cc=bonzini@gnu.org \
    --cc=ehabkost@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=sw@weilnetz.de \
    /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.