From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists1p.gnu.org (lists1p.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 30D6F606A31A for ; Fri, 23 Oct 2026 16:59:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key, unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=RYoTBO5o Received: from localhost ([::1] helo=lists1p.gnu.org) by lists1p.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1xKIbZ-0003oL-RY; Fri, 23 Oct 2026 12:58:57 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists1p.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1xKIbS-0003na-Lu for qemu-devel@nongnu.org; Fri, 23 Oct 2026 12:58:51 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1xKIbQ-0006P7-Fd for qemu-devel@nongnu.org; Fri, 23 Oct 2026 12:58:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1792774726; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=JjTmzfgRIgsxdv35pL8NePUUPwmcEndqQsMdTszIkMo=; b=RYoTBO5o0h3WzEeBCjIwH5feTfplvqrSgmvBakzgo7MxTjBHBwIbmG6MQLxkvTD1TN+9tO lflnbtgwDegEyTIRvo59U286KZVy22v9fedkhbrtWNCUfTnAdoU2o442Wf0dYUaNbOP/S+ QcDQGD37oksv1MnXXx5G4kMcZM9Wmsg= Received: from mx-prod-mc-05.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-170-FAklahg6NF-nmwY-QJ-dMA-1; Fri, 23 Oct 2026 12:58:42 -0400 X-MC-Unique: FAklahg6NF-nmwY-QJ-dMA-1 X-Mimecast-MFC-AGG-ID: FAklahg6NF-nmwY-QJ-dMA_1792774721 Received: from mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.93]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 656B81956052; Fri, 23 Oct 2026 16:58:41 +0000 (UTC) Received: from redhat.com (headnet04.pony-001.prod.iad2.dc.redhat.com [10.2.32.116]) by mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 890C018004D2; Fri, 23 Oct 2026 16:58:38 +0000 (UTC) Date: Fri, 23 Oct 2026 17:58:35 +0100 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= To: Stefano Garzarella Cc: qemu-devel@nongnu.org, Dorinda Bassey , Stefan Hajnoczi , Albert Esteve , "Michael S. Tsirkin" , Pierrick Bouvier , vhost-user@lists.linux.dev Subject: Re: [PATCH] vhost-user: add dedicated mailing list Message-ID: References: <20261023162441.89450-1-sgarzare@redhat.com> X-Archived-By: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20261023162441.89450-1-sgarzare@redhat.com> User-Agent: Mutt/2.4.2 (2026-08-30) X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.93 Received-SPF: pass client-ip=170.10.133.124; envelope-from=berrange@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: 2 X-Spam_score: 0.2 X-Spam_bar: / X-Spam_report: (0.2 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.339, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_SBL_CSS=3.335, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: qemu development List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Sender: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org X-Spam-Status: No, score=-17.6 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_CR_TRAILER,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_PASS, SPF_PASS,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=4.0.1 X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on aws-us-west-2-korg-listserv-alma10-1 On Fri, Oct 23, 2026 at 06:24:40PM +0200, Stefano Garzarella wrote: > From: Stefano Garzarella > > During the "Virtio and Vhost-User Ecosystem for Production and > Automotive Systems" BoF at LPC 2026 [1] we discussed and agreed on > creating a new vhost-user mailing list, mainly for changes to the > specification and discussions around the protocol. You say the list is for discussions around the spec / protocol, but... > The main reason is that the vhost-user specification is also used > by other VMMs and implemented by several back-ends outside the QEMU > repository, whose developers often do not follow qemu-devel. > > Add a paragraph in the specification about the new mailing list and > a dedicated MAINTAINERS entry for the vhost-user protocol, covering > the specification, the QEMU front-end and libvhost-user (back-end > library). ...this MAINTAINERS addition means the mailing list will be CC'd on all code patches sent to QEMU for those file patterns. Are you sure that's content that members of the list want to be sent unconditionally ? > > [1] https://lpc.events/event/20/contributions/2365/ > > Signed-off-by: Stefano Garzarella > --- > MAINTAINERS | 12 ++++++++++-- > docs/interop/vhost-user.rst | 6 ++++++ > 2 files changed, 16 insertions(+), 2 deletions(-) > > diff --git a/MAINTAINERS b/MAINTAINERS > index d9209f043f..dcdb65d8cb 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -2532,19 +2532,27 @@ M: Michael S. Tsirkin > R: Stefano Garzarella > S: Supported > F: hw/*/*vhost* > -F: docs/interop/vhost-user* > F: docs/system/devices/virtio/vhost-user* > F: contrib/vhost-user-*/ > F: backends/*vhost* > F: include/system/vhost-user-backend.h > F: include/hw/virtio/vhost* > F: include/*/vhost* > -F: subprojects/libvhost-user/ > F: block/export/vhost-user* > F: util/vhost-user-server.c > F: net/vhost* > F: tests/functional/x86_64/test_vhost_user_bridge.py > > +vhost-user protocol > +M: Michael S. Tsirkin > +R: Stefano Garzarella > +L: vhost-user@lists.linux.dev > +S: Supported > +F: docs/interop/vhost-user* > +F: hw/virtio/vhost-user.c > +F: include/hw/virtio/vhost-user.h > +F: subprojects/libvhost-user/ > + > vhost-shadow-virtqueue > R: Eugenio Pérez > F: hw/virtio/vhost-shadow-virtqueue.* > diff --git a/docs/interop/vhost-user.rst b/docs/interop/vhost-user.rst > index c1e02ff7e9..198ad30f5c 100644 > --- a/docs/interop/vhost-user.rst > +++ b/docs/interop/vhost-user.rst > @@ -38,6 +38,12 @@ conventions `. > The *front-end* and *back-end* can be either a client (i.e. connecting) or > server (listening) in the socket communication. > > +The protocol is developed and discussed on the `vhost-user mailing list > +`_, archived at > +https://lore.kernel.org/vhost-user/. Until October 2026, when this list > +was created, discussions took place on the qemu-devel mailing list, > +archived at https://lore.kernel.org/qemu-devel/. > + > Support for platforms other than Linux > -------------------------------------- > > -- > 2.56.0 > > With regards, Daniel -- |: https://berrange.com ~~ https://hachyderm.io/@berrange :| |: https://libvirt.org ~~ https://entangle-photo.org :| |: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|