From: Juergen Gross <jgross@suse.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>, xen-devel@lists.xenproject.org
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
x86@kernel.org, Andrew Jones <drjones@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] x86/xen: put setup.c, pmu.c and apic.c under CONFIG_XEN_PV
Date: Wed, 1 Mar 2017 08:10:58 +0100 [thread overview]
Message-ID: <61dd883f-9ba6-598d-5a69-39dbf4d0b258@suse.com> (raw)
In-Reply-To: <20170224161440.2136-5-vkuznets@redhat.com>
On 24/02/17 17:14, Vitaly Kuznetsov wrote:
> xen_pmu_init/finish() functions are used in suspend.c and
> enlighten.c, add stubs for now.
>
> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-03-01 7:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170224161440.2136-1-vkuznets@redhat.com>
2017-02-24 16:14 ` [PATCH 1/5] x86/xen: start untangling PV and PVHVM guest support code Vitaly Kuznetsov
2017-02-24 16:14 ` [PATCH 2/5] x86/xen: split smp.c for PV and PVHVM guests Vitaly Kuznetsov
2017-03-01 6:24 ` Juergen Gross
2017-02-24 16:14 ` [PATCH 3/5] x86/xen: put setup.c, mmu.c and p2m.c under CONFIG_XEN_PV Vitaly Kuznetsov
2017-03-01 6:25 ` Juergen Gross
2017-02-24 16:14 ` [PATCH 4/5] x86/xen: put setup.c, pmu.c and apic.c " Vitaly Kuznetsov
2017-02-24 16:14 ` [PATCH 5/5] x86/xen: split suspend.c for PV and PVHVM guests Vitaly Kuznetsov
2017-03-01 7:14 ` Juergen Gross
[not found] ` <20170224161440.2136-2-vkuznets@redhat.com>
2017-03-01 6:22 ` [PATCH 1/5] x86/xen: start untangling PV and PVHVM guest support code Juergen Gross
2017-03-01 9:38 ` Vitaly Kuznetsov
[not found] ` <20170224161440.2136-5-vkuznets@redhat.com>
2017-03-01 7:10 ` Juergen Gross [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=61dd883f-9ba6-598d-5a69-39dbf4d0b258@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=drjones@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vkuznets@redhat.com \
--cc=x86@kernel.org \
--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 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).