public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Brett Creeley <bcreeley@amd.com>
To: Christoph Hellwig <hch@infradead.org>,
	Brett Creeley <brett.creeley@amd.com>
Cc: kvm@vger.kernel.org, netdev@vger.kernel.org,
	alex.williamson@redhat.com, cohuck@redhat.com, jgg@nvidia.com,
	yishaih@nvidia.com, shameerali.kolothum.thodi@huawei.com,
	kevin.tian@intel.com, shannon.nelson@amd.com,
	drivers@pensando.io
Subject: Re: [RFC PATCH v2 vfio 0/7] pds vfio driver
Date: Thu, 15 Dec 2022 14:22:36 -0800	[thread overview]
Message-ID: <4438c3bc-0bb2-becb-48ad-4e85f79f240f@amd.com> (raw)
In-Reply-To: <Y5rE26OcSnoZbqzn@infradead.org>

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

      reply	other threads:[~2022-12-15 22:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14 23:21 [RFC PATCH v2 vfio 0/7] pds vfio driver Brett Creeley
2022-12-14 23:21 ` [RFC PATCH v2 vfio 1/7] vfio/pds: Initial support for pds_vfio VFIO driver Brett Creeley
2023-01-03 12:12   ` liulongfang
2023-01-03 18:38     ` Shannon Nelson
2022-12-14 23:21 ` [RFC PATCH v2 vfio 2/7] vfio/pds: Add support to register as PDS client Brett Creeley
2022-12-14 23:21 ` [RFC PATCH v2 vfio 3/7] vfio/pds: Add VFIO live migration support Brett Creeley
2023-01-03 12:25   ` liulongfang
2023-01-03 20:23     ` Shannon Nelson
2022-12-14 23:21 ` [RFC PATCH v2 vfio 4/7] vfio: Commonize combine_ranges for use in other VFIO drivers Brett Creeley
2022-12-14 23:21 ` [RFC PATCH v2 vfio 5/7] vfio/pds: Add support for dirty page tracking Brett Creeley
2022-12-14 23:21 ` [RFC PATCH v2 vfio 6/7] vfio/pds: Add support for firmware recovery Brett Creeley
2022-12-14 23:21 ` [RFC PATCH v2 vfio 7/7] vfio/pds: Add Kconfig and documentation Brett Creeley
2022-12-15  6:55 ` [RFC PATCH v2 vfio 0/7] pds vfio driver Christoph Hellwig
2022-12-15 22:22   ` Brett Creeley [this message]

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=4438c3bc-0bb2-becb-48ad-4e85f79f240f@amd.com \
    --to=bcreeley@amd.com \
    --cc=alex.williamson@redhat.com \
    --cc=brett.creeley@amd.com \
    --cc=cohuck@redhat.com \
    --cc=drivers@pensando.io \
    --cc=hch@infradead.org \
    --cc=jgg@nvidia.com \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shameerali.kolothum.thodi@huawei.com \
    --cc=shannon.nelson@amd.com \
    --cc=yishaih@nvidia.com \
    /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