From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 59925986653 for ; Wed, 18 Jan 2023 13:29:55 +0000 (UTC) Date: Wed, 18 Jan 2023 08:29:45 -0500 From: "Michael S. Tsirkin" Message-ID: <20230118082858-mutt-send-email-mst@kernel.org> References: <961D315C9D3A523B+202301111121345064138@sudoinfotech.com> <40a63ca5-1273-d334-8d81-d5880e4fdff1@nvidia.com> <1DDD350DC1DCE386+2023011811234242045568@sudoinfotech.com> <9b0655f9-cf97-8d9a-cfd9-bf756821d7e3@nvidia.com> <20230118060518-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 In-Reply-To: Subject: Re: [virtio-comment] About adding a new device type virtio-nvme Content-Type: text/plain; charset=us-ascii Content-Disposition: inline To: Max Gurtovoy Cc: =?utf-8?B?5L6v6Iux5LmQ?= , Stefan Hajnoczi , virtio-comment , Christoph Hellwig , Keith Busch , Kevin Wolf , Klaus Jensen , sgarzare List-ID: On Wed, Jan 18, 2023 at 01:27:35PM +0200, Max Gurtovoy wrote: > What I don't understand is why we can't start merging the infrastructure we > worked on almost 2 years in parallel to unrelated vDPA efforts. Is all this pertinent to the virtio specification in some way? -- MST This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: virtio-comment-subscribe@lists.oasis-open.org Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org List help: virtio-comment-help@lists.oasis-open.org List archive: https://lists.oasis-open.org/archives/virtio-comment/ Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists Committee: https://www.oasis-open.org/committees/virtio/ Join OASIS: https://www.oasis-open.org/join/