[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] GDBSX Maintainer

To: Elena Ufimtseva <ufimtseva@xxxxxxxxx>
From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date: Tue, 28 Jun 2016 17:53:37 +0100
Cc: Julien Grall <julien.grall@xxxxxxx>, Xen Devel <xen-devel@xxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxx>
Delivery-date: Tue, 28 Jun 2016 16:54:12 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 28/06/16 17:52, Elena Ufimtseva wrote:
> Hi Julien, Andrew
>
> I was talking to Konrad some time ago about looking into this and the
> possibility of maintaining gdbsx code. I am willing sign up for this
> if there are no objections.

Fine by me.  The traditional way of doing this would be for you to
author a patch changing the mantainers file.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

References:
- [Xen-devel] GDBSX Maintainer
  - From: Julien Grall
- Re: [Xen-devel] GDBSX Maintainer
  - From: Andrew Cooper
- Re: [Xen-devel] GDBSX Maintainer
  - From: Elena Ufimtseva

Prev by Date: Re: [Xen-devel] GDBSX Maintainer
Next by Date: Re: [Xen-devel] [PATCH v5 05/17] xen/passthrough: x86: Use INVALID_GFN rather than INVALID_MFN
Previous by thread: Re: [Xen-devel] GDBSX Maintainer
Next by thread: [Xen-devel] [PATCH] xen/arm: io: Protect the handlers with a read-write lock
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.