From: Paul Durrant <Paul.Durrant@citrix.com>
To: 'Jan Beulich' <JBeulich@suse.com>
Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 1/8] viridian: move the code into its own sub-directory
Date: Wed, 31 Oct 2018 10:30:37 +0000 [thread overview]
Message-ID: <37925c0de5324f4b96ecf46734aebd17@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <5BD9814E02000078001F6ACE@prv1-mh.provo.novell.com>
> -----Original Message-----
> From: Jan Beulich [mailto:JBeulich@suse.com]
> Sent: 31 October 2018 10:18
> To: Paul Durrant <Paul.Durrant@citrix.com>
> Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>; Wei Liu
> <wei.liu2@citrix.com>; xen-devel <xen-devel@lists.xenproject.org>
> Subject: Re: [PATCH 1/8] viridian: move the code into its own sub-
> directory
>
> >>> On 29.10.18 at 19:02, <paul.durrant@citrix.com> wrote:
> > Subsequent patches will introduce support for more viridian
> enlightenments
> > which will make a single source module quite lengthy.
> >
> > This patch therefore creates a new arch/x86/hvm/viridian sub-directory
> and
> > moves viridian.c into that.
> >
> > The patch also fixes some bad whitespace whilst moving the code.
> >
> > Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
> > ---
> > Cc: Jan Beulich <jbeulich@suse.com>
> > Cc: Andrew Cooper <andrew.cooper3@citrix.com>
> > Cc: Wei Liu <wei.liu2@citrix.com>
> > ---
> > xen/arch/x86/hvm/Makefile | 2 +-
> > xen/arch/x86/hvm/viridian/Makefile | 1 +
> > xen/arch/x86/hvm/{ => viridian}/viridian.c | 4 ++--
> > 3 files changed, 4 insertions(+), 3 deletions(-)
> > create mode 100644 xen/arch/x86/hvm/viridian/Makefile
> > rename xen/arch/x86/hvm/{ => viridian}/viridian.c (99%)
>
> Actually, I now realize that my ack is dependent on you also
> adjusting ./MAINTAINERS here, or else you will cease to be
> maintainer of this code.
>
Oh. Good spot. I'll fold that change into v2 of this patch.
Paul
> Jan
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-10-31 10:30 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 18:02 [PATCH 0/8] viridian cleanup Paul Durrant
2018-10-29 18:02 ` [PATCH 1/8] viridian: move the code into its own sub-directory Paul Durrant
2018-10-30 9:25 ` Jan Beulich
2018-10-31 10:17 ` Jan Beulich
2018-10-31 10:30 ` Paul Durrant [this message]
2018-10-29 18:02 ` [PATCH 1/2] x86/mm/p2m: don't needlessly limit MMIO mapping order to 4k Paul Durrant
2018-10-29 18:03 ` Paul Durrant
2018-10-29 18:02 ` [PATCH 2/2] iommu / p2m: add a page_order parameter to iommu_map/unmap_page() Paul Durrant
2018-10-29 18:03 ` Paul Durrant
2018-10-29 18:02 ` [PATCH 2/8] viridian: remove MSR perf counters Paul Durrant
2018-10-30 16:25 ` Roger Pau Monné
2018-10-29 18:02 ` [PATCH 3/8] viridian: remove comments referencing section number in the spec Paul Durrant
2018-10-30 16:34 ` Roger Pau Monné
2018-10-30 17:07 ` Paul Durrant
2018-10-29 18:02 ` [PATCH 4/8] viridian: remove duplicate union types Paul Durrant
2018-10-30 16:40 ` Roger Pau Monné
2018-10-30 17:03 ` Paul Durrant
2018-10-31 8:44 ` Roger Pau Monné
2018-10-29 18:02 ` [PATCH 5/8] viridian: separate interrupt related enlightenment implementations Paul Durrant
2018-10-30 16:52 ` Roger Pau Monné
2018-10-30 17:06 ` Paul Durrant
2018-10-29 18:02 ` [PATCH 6/8] viridian: separate time " Paul Durrant
2018-10-30 17:03 ` Roger Pau Monné
2018-10-30 17:08 ` Paul Durrant
2018-10-29 18:02 ` [PATCH 7/8] viridian: define type for the 'virtual VP assist page' Paul Durrant
2018-10-30 17:08 ` Roger Pau Monné
2018-10-30 17:11 ` Paul Durrant
2018-10-31 8:53 ` Roger Pau Monné
2018-10-31 9:27 ` Paul Durrant
2018-10-31 9:41 ` Jan Beulich
2018-10-31 10:01 ` Paul Durrant
2018-10-31 10:16 ` Jan Beulich
2018-10-29 18:02 ` [PATCH 8/8] viridian: introduce struct viridian_page Paul Durrant
2018-10-30 17:17 ` Roger Pau Monné
2018-10-30 17:25 ` Paul Durrant
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=37925c0de5324f4b96ecf46734aebd17@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=JBeulich@suse.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 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).