| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 5 Jun 2013 14:21:17 +0100 From: Catalin Marinas <catalin.marinas@....com> To: Stefano Stabellini <stefano.stabellini@...citrix.com> Cc: "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>, Will Deacon <Will.Deacon@....com>, "Ian.Campbell@...rix.com" <Ian.Campbell@...rix.com>, "konrad.wilk@...cle.com" <konrad.wilk@...cle.com> Subject: Re: [PATCH v2 5/5] arm64/xen: introduce CONFIG_XEN and hypercall.S on ARM64 On Mon, Jun 03, 2013 at 05:51:53PM +0100, Stefano Stabellini wrote: > On Mon, 3 Jun 2013, Catalin Marinas wrote: > > Otherwise, the series looks good. How do you plan to upstream this? > > Good question. > Traditionally Xen stuff goes to Linus directly via one of the Xen trees > (Konrad's or mine), but since this is the very first Xen patch series > for arm64 if you prefer I can submit a pull request to you instead. > Just let me know, I am happy either way. I can take the first series and subsequent merges can go via the Xen tree (KVM has a similar approach). > In any case, are you OK with sending it upstream during the next merge > window? Yes, if I get a pull request in time ;) -- Catalin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists