From: Andrew Cooper <amc96@srcf.net>
To: Xenia Ragiadakou <burzalodowa@gmail.com>, xen-devel@lists.xenproject.org
Cc: "Paul Durrant" <paul@xen.org>, "Jan Beulich" <jbeulich@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>, "Wei Liu" <wl@xen.org>
Subject: Re: [PATCH 0/2] Remove unused virtualization technology specific headers
Date: Fri, 27 Jan 2023 09:54:05 +0000 [thread overview]
Message-ID: <9718888d-96a9-09fb-fca9-f12fa76929f3@srcf.net> (raw)
In-Reply-To: <20230127094656.140120-1-burzalodowa@gmail.com>
On 27/01/2023 9:46 am, Xenia Ragiadakou wrote:
> The patches remove forgotten and now unused virtualization technology specific
> headers from arch/x86/cpu/vpmu.c and arch/x86/hvm/emulate.c.
>
> Xenia Ragiadakou (2):
> x86/emulate: remove unused svm specific header
> x86/vpmu: remove unused svm and vmx specific headers
>
> xen/arch/x86/cpu/vpmu.c | 4 ----
> xen/arch/x86/hvm/emulate.c | 1 -
> 2 files changed, 5 deletions(-)
>
Oh excellent. Acked-by: Andrew Cooper <andrew.cooper3@citrix.com>
IMO the fixes tags are useful even if we won't want to backport them.
It's an easy pointer for people to follow if needs be.
~Andrew
prev parent reply other threads:[~2023-01-27 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 9:46 [PATCH 0/2] Remove unused virtualization technology specific headers Xenia Ragiadakou
2023-01-27 9:46 ` [PATCH 1/2] x86/emulate: remove unused svm specific header Xenia Ragiadakou
2023-01-27 9:46 ` [PATCH 2/2] x86/vpmu: remove unused svm and vmx specific headers Xenia Ragiadakou
2023-01-27 9:54 ` Andrew Cooper [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=9718888d-96a9-09fb-fca9-f12fa76929f3@srcf.net \
--to=amc96@srcf.net \
--cc=andrew.cooper3@citrix.com \
--cc=burzalodowa@gmail.com \
--cc=jbeulich@suse.com \
--cc=paul@xen.org \
--cc=roger.pau@citrix.com \
--cc=wl@xen.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 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.