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
| ||
|
Message-ID: <4438c3bc-0bb2-becb-48ad-4e85f79f240f@amd.com> Date: Thu, 15 Dec 2022 14:22:36 -0800 From: Brett Creeley <bcreeley@....com> To: Christoph Hellwig <hch@...radead.org>, Brett Creeley <brett.creeley@....com> Cc: kvm@...r.kernel.org, netdev@...r.kernel.org, alex.williamson@...hat.com, cohuck@...hat.com, jgg@...dia.com, yishaih@...dia.com, shameerali.kolothum.thodi@...wei.com, kevin.tian@...el.com, shannon.nelson@....com, drivers@...sando.io Subject: Re: [RFC PATCH v2 vfio 0/7] pds vfio driver On 12/14/2022 10:55 PM, Christoph Hellwig wrote: > just as said last time and completely ignored by you: any nvme live > migration needs to be standardized in the NVMe technical working group > before it can be merged in Linux. Hey Christoph, I'm not trying to ignore you and that's why this series is still marked RFC. I appreciate the feedback, regardless of the end result. I am paying attention to the other thread on the KVM mailing list and do understand your stance on the topic. Thanks, Brett
Powered by blists - more mailing lists