From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Wei Liu <wei.liu2@citrix.com>, Jan Beulich <JBeulich@suse.com>,
George Dunlap <george.dunlap@citrix.com>
Cc: Tamas K Lengyel <tamas@tklengyel.com>,
Adrian Pop <apop@bitdefender.com>,
Sergej Proskurin <proskurin@sec.in.tum.de>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v2] x86/altp2m: Allow setting the #VE info page for an arbitrary VCPU
Date: Thu, 20 Sep 2018 11:38:04 +0300 [thread overview]
Message-ID: <745d932d-4dd3-4ceb-dc6f-8abf39b65672@bitdefender.com> (raw)
In-Reply-To: <20180920083109.a6useayrolg5rhtl@zion.uk.xensource.com>
On 9/20/18 11:31 AM, Wei Liu wrote:
>>>> Reviewed-by: Tamas K Lengyel <tamas@tklengyel.com>
>>> Are there any issues preventing this patch to go in? Possibly missing acks?
>> Well, afaics the patch has no x86 maintainer ack, nor - considering it's
>> an mm function sitting in the "wrong" file, at least one from the mm
>> maintainer. As mentioned a number of times before, it is the submitter's
>> responsibility to chase acks, not the committers' or maintainers'.
>
> Oh, sorry. I have missed that this at least needs an ack from George.
> I will wait until EOD for George to give an ack. If there isn't one by
> then I will revert the patch in staging.
Added George to the email recipients.
Thanks,
Razvan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-09-20 8:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 4:59 [PATCH v2] x86/altp2m: Allow setting the #VE info page for an arbitrary VCPU Adrian Pop
2018-09-04 20:40 ` Tamas K Lengyel
2018-09-04 20:58 ` Razvan Cojocaru
2018-09-05 6:56 ` Jan Beulich
2018-09-05 8:11 ` Razvan Cojocaru
2018-09-05 8:14 ` Razvan Cojocaru
2018-09-05 9:27 ` Jan Beulich
2018-09-05 16:28 ` Tamas K Lengyel
2018-09-05 16:40 ` Razvan Cojocaru
2018-09-05 18:40 ` Tamas K Lengyel
2018-09-05 18:45 ` Andrew Cooper
2018-09-05 22:27 ` Tamas K Lengyel
2018-09-20 8:11 ` Razvan Cojocaru
2018-09-20 8:14 ` Wei Liu
2018-09-20 8:16 ` Razvan Cojocaru
2018-09-20 8:22 ` Jan Beulich
2018-09-20 8:31 ` Wei Liu
2018-09-20 8:38 ` Razvan Cojocaru [this message]
2018-09-20 8:33 ` Jan Beulich
2018-09-05 18:53 ` Razvan Cojocaru
2018-09-20 14:42 ` George Dunlap
2018-09-20 14:55 ` Razvan Cojocaru
2018-09-20 15:28 ` George Dunlap
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=745d932d-4dd3-4ceb-dc6f-8abf39b65672@bitdefender.com \
--to=rcojocaru@bitdefender.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=apop@bitdefender.com \
--cc=george.dunlap@citrix.com \
--cc=proskurin@sec.in.tum.de \
--cc=tamas@tklengyel.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 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.