[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH V3] tools/libxc, xen/x86: Added xc_set_mem_access_multi()
- To: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>, George Dunlap <george.dunlap@xxxxxxxxxx>
- From: Julien Grall <julien.grall@xxxxxxx>
- Date: Tue, 6 Sep 2016 12:57:40 +0100
- Cc: sstabellini@xxxxxxxxxx, wei.liu2@xxxxxxxxxx, Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx>, george.dunlap@xxxxxxxxxxxxx, andrew.cooper3@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxx, tamas@xxxxxxxxxxxxx, jbeulich@xxxxxxxx
- Delivery-date: Tue, 06 Sep 2016 11:57:52 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
On 06/09/16 12:51, Ian Jackson wrote:
George Dunlap writes ("Re: [PATCH V3] tools/libxc, xen/x86: Added
xc_set_mem_access_multi()"):
So you really don't mind if Razvan submits a patch for code that he
hasn't tested and isn't sure works?
I don't think that's a very good idea. (Are there possible security
implications? It's not entirely clear to me...)
Under the circumstances I don't think it's reasonable to expect Razvan
to write the patch, unless some ARM maintainer is willing to test it.
That was implied from my side. It has been done recently on other
various patches which require modifications in the ARM code.
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel
|
