From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1A42258AAA for ; Fri, 16 Feb 2024 11:09:02 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.133.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708081745; cv=none; b=APZXmJtqBxysA+GbDBsSQQuEHXBv718pf2j7cNYgTn7aJiFRVlNP7EQdq+JqmhDfOKS//7dG6ZO4OwHGfNOezEYrhEHCjKcGVDxB3R60xIUF/P8T2RZXugfgRqHf0zPKZIiAUbcHxy9g98VfDhMWvhWgsWyKL8HbhbS2C0SMYmc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708081745; c=relaxed/simple; bh=Bm2pxnDRCF5Y+3itulmeyIU/eDYa4Yt71dv1HrtiDn0=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=UIcXVUy+Jf3GdZ03nCEjBBJZN9T7BsVp0lwe/9U3rtPr0SX8E+Z1kY0XWrfgVafNXi2HQw3S/jKzywBA2sZXiM3vCGszFyiP0jX6m48+b12NaOC+7UvW3CRGsn733G/4fm5xvYWXD46xsTmgJ89cFCR+LI+5lZPWyDUXSM9bm4c= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=Lyo9/29i; arc=none smtp.client-ip=170.10.133.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="Lyo9/29i" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1708081741; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Bm2pxnDRCF5Y+3itulmeyIU/eDYa4Yt71dv1HrtiDn0=; b=Lyo9/29izOv7hX+MB3805efuk8BmS0Qw32H2CUyvDXdrJUSPih9dqh5ri/kHlgLbsk7k0p yOfZ2XEtuDka7xDn2j3HrfdeEzTf0XyjaxKOTHacnHjVI/a21VI1/7qqkPT9h0opH/RM6y FLwwu5evChhe0RyTuo+9+/bclm2vg3Y= Received: from mimecast-mx02.redhat.com (mx-ext.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-624-Om2yKeRtMS-jnZAO24u_lA-1; Fri, 16 Feb 2024 06:08:58 -0500 X-MC-Unique: Om2yKeRtMS-jnZAO24u_lA-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (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 mimecast-mx02.redhat.com (Postfix) with ESMTPS id 9F0571C04180; Fri, 16 Feb 2024 11:08:57 +0000 (UTC) Received: from localhost (dhcp-192-239.str.redhat.com [10.33.192.239]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 5CD862166B4F; Fri, 16 Feb 2024 11:08:57 +0000 (UTC) From: Cornelia Huck To: Mikhail Golubev-Ciuchea , virtio-comment@lists.oasis-open.org, virtio-dev@lists.oasis-open.org, linux-can@vger.kernel.org Cc: Harald Mommer , Mikhail Golubev-Ciuchea Subject: Re: [virtio-dev] [RFC PATCH v3] virtio-can: Device specification. In-Reply-To: <20230609142243.199074-1-Mikhail.Golubev-Ciuchea@opensynergy.com> Organization: "Red Hat GmbH, Sitz: Werner-von-Siemens-Ring 12, D-85630 Grasbrunn, Handelsregister: Amtsgericht =?utf-8?Q?M=C3=BCnchen=2C?= HRB 153243, =?utf-8?Q?Gesch=C3=A4ftsf=C3=BChrer=3A?= Ryan Barnhart, Charles Cachera, Michael O'Neill, Amy Ross" References: <20230609142243.199074-1-Mikhail.Golubev-Ciuchea@opensynergy.com> User-Agent: Notmuch/0.37 (https://notmuchmail.org) Date: Fri, 16 Feb 2024 12:08:56 +0100 Message-ID: <87sf1sfyyf.fsf@redhat.com> Precedence: bulk X-Mailing-List: linux-can@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.6 On Fri, Jun 09 2023, Mikhail Golubev-Ciuchea wrote: > From: Harald Mommer > > virtio-can is a virtual CAN device. It provides a way to give access to > a CAN controller from a driver guest. The device is aimed to be used by > driver guests running a HLOS as well as by driver guests running a > typical RTOS as used in controller environments. > > Signed-off-by: Harald Mommer > Signed-off-by: Mikhail Golubev-Ciuchea (...) > diff --git a/device-types/can/device-conformance.tex b/device-types/can/device-conformance.tex > new file mode 100644 > index 0000000..f944ffd > --- /dev/null > +++ b/device-types/can/device-conformance.tex > @@ -0,0 +1,8 @@ > +\conformance{\subsection}{CAN Device Conformance}\label{sec:Conformance / Device Conformance / CAN Device Conformance} > + > +A CAN device MUST conform to the following normative statements: > + > +\begin{itemize} > +\item \ref{devicenormative:Device Types / CAN Device / Feature bits} I just noticed that this introduces[1] an undefined reference (there's no device normative section for feature bits.) I'd suggest to just drop this reference (I can do that as a simple editorial update); if we want to have an actual normative reference for feature bits, it should be done via an extra change on top. > +\item \ref{devicenormative:Device Types / CAN Device / Device Operation / CAN Message Transmission} > +\end{itemize} [1] Easy to miss, as the current 1.4 branch has a pre-existing undefined reference, which will go away once we finally can merge into the main branch again and have all that craziness go away after we manage to do the actual 1.3 release :/ From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from ws5-mx01.kavi.com (ws5-mx01.kavi.com [34.193.7.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 0F054C48BEB for ; Fri, 16 Feb 2024 11:09:09 +0000 (UTC) Received: from lists.oasis-open.org (oasis.ws5.connectedcommunity.org [10.110.1.242]) by ws5-mx01.kavi.com (Postfix) with ESMTP id CDC44C6222 for ; Fri, 16 Feb 2024 11:09:05 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id B906598666D for ; Fri, 16 Feb 2024 11:09:05 +0000 (UTC) Received: from host09.ws5.connectedcommunity.org (host09.ws5.connectedcommunity.org [10.110.1.97]) by lists.oasis-open.org (Postfix) with QMQP id A5AAE986602; Fri, 16 Feb 2024 11:09:05 +0000 (UTC) Mailing-List: contact virtio-comment-help@lists.oasis-open.org; run by ezmlm List-ID: Sender: Precedence: bulk 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 97BAD9865FF for ; Fri, 16 Feb 2024 11:09:05 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: Om2yKeRtMS-jnZAO24u_lA-1 From: Cornelia Huck To: Mikhail Golubev-Ciuchea , virtio-comment@lists.oasis-open.org, virtio-dev@lists.oasis-open.org, linux-can@vger.kernel.org Cc: Harald Mommer , Mikhail Golubev-Ciuchea In-Reply-To: <20230609142243.199074-1-Mikhail.Golubev-Ciuchea@opensynergy.com> Organization: "Red Hat GmbH, Sitz: Werner-von-Siemens-Ring 12, D-85630 Grasbrunn, Handelsregister: Amtsgericht =?utf-8?Q?M=C3=BCnchen=2C?= HRB 153243, =?utf-8?Q?Gesch=C3=A4ftsf=C3=BChrer=3A?= Ryan Barnhart, Charles Cachera, Michael O'Neill, Amy Ross" References: <20230609142243.199074-1-Mikhail.Golubev-Ciuchea@opensynergy.com> User-Agent: Notmuch/0.37 (https://notmuchmail.org) Date: Fri, 16 Feb 2024 12:08:56 +0100 Message-ID: <87sf1sfyyf.fsf@redhat.com> MIME-Version: 1.0 Content-Type: text/plain X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.6 Subject: [virtio-comment] Re: [virtio-dev] [RFC PATCH v3] virtio-can: Device specification. On Fri, Jun 09 2023, Mikhail Golubev-Ciuchea wrote: > From: Harald Mommer > > virtio-can is a virtual CAN device. It provides a way to give access to > a CAN controller from a driver guest. The device is aimed to be used by > driver guests running a HLOS as well as by driver guests running a > typical RTOS as used in controller environments. > > Signed-off-by: Harald Mommer > Signed-off-by: Mikhail Golubev-Ciuchea (...) > diff --git a/device-types/can/device-conformance.tex b/device-types/can/device-conformance.tex > new file mode 100644 > index 0000000..f944ffd > --- /dev/null > +++ b/device-types/can/device-conformance.tex > @@ -0,0 +1,8 @@ > +\conformance{\subsection}{CAN Device Conformance}\label{sec:Conformance / Device Conformance / CAN Device Conformance} > + > +A CAN device MUST conform to the following normative statements: > + > +\begin{itemize} > +\item \ref{devicenormative:Device Types / CAN Device / Feature bits} I just noticed that this introduces[1] an undefined reference (there's no device normative section for feature bits.) I'd suggest to just drop this reference (I can do that as a simple editorial update); if we want to have an actual normative reference for feature bits, it should be done via an extra change on top. > +\item \ref{devicenormative:Device Types / CAN Device / Device Operation / CAN Message Transmission} > +\end{itemize} [1] Easy to miss, as the current 1.4 branch has a pre-existing undefined reference, which will go away once we finally can merge into the main branch again and have all that craziness go away after we manage to do the actual 1.3 release :/ 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/ From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from ws5-mx01.kavi.com (ws5-mx01.kavi.com [34.193.7.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 1BC1DC48BEB for ; Fri, 16 Feb 2024 11:09:04 +0000 (UTC) Received: from lists.oasis-open.org (oasis.ws5.connectedcommunity.org [10.110.1.242]) by ws5-mx01.kavi.com (Postfix) with ESMTP id 4F8867C1AB for ; Fri, 16 Feb 2024 11:09:04 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 1D8B3986668 for ; Fri, 16 Feb 2024 11:09:04 +0000 (UTC) Received: from host09.ws5.connectedcommunity.org (host09.ws5.connectedcommunity.org [10.110.1.97]) by lists.oasis-open.org (Postfix) with QMQP id F09589865FD; Fri, 16 Feb 2024 11:09:03 +0000 (UTC) Mailing-List: contact virtio-dev-help@lists.oasis-open.org; run by ezmlm List-ID: Sender: Precedence: bulk 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 E1C15986602 for ; Fri, 16 Feb 2024 11:09:03 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: Om2yKeRtMS-jnZAO24u_lA-1 From: Cornelia Huck To: Mikhail Golubev-Ciuchea , virtio-comment@lists.oasis-open.org, virtio-dev@lists.oasis-open.org, linux-can@vger.kernel.org Cc: Harald Mommer , Mikhail Golubev-Ciuchea In-Reply-To: <20230609142243.199074-1-Mikhail.Golubev-Ciuchea@opensynergy.com> Organization: "Red Hat GmbH, Sitz: Werner-von-Siemens-Ring 12, D-85630 Grasbrunn, Handelsregister: Amtsgericht =?utf-8?Q?M=C3=BCnchen=2C?= HRB 153243, =?utf-8?Q?Gesch=C3=A4ftsf=C3=BChrer=3A?= Ryan Barnhart, Charles Cachera, Michael O'Neill, Amy Ross" References: <20230609142243.199074-1-Mikhail.Golubev-Ciuchea@opensynergy.com> User-Agent: Notmuch/0.37 (https://notmuchmail.org) Date: Fri, 16 Feb 2024 12:08:56 +0100 Message-ID: <87sf1sfyyf.fsf@redhat.com> MIME-Version: 1.0 Content-Type: text/plain X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.6 Subject: Re: [virtio-dev] [RFC PATCH v3] virtio-can: Device specification. On Fri, Jun 09 2023, Mikhail Golubev-Ciuchea wrote: > From: Harald Mommer > > virtio-can is a virtual CAN device. It provides a way to give access to > a CAN controller from a driver guest. The device is aimed to be used by > driver guests running a HLOS as well as by driver guests running a > typical RTOS as used in controller environments. > > Signed-off-by: Harald Mommer > Signed-off-by: Mikhail Golubev-Ciuchea (...) > diff --git a/device-types/can/device-conformance.tex b/device-types/can/device-conformance.tex > new file mode 100644 > index 0000000..f944ffd > --- /dev/null > +++ b/device-types/can/device-conformance.tex > @@ -0,0 +1,8 @@ > +\conformance{\subsection}{CAN Device Conformance}\label{sec:Conformance / Device Conformance / CAN Device Conformance} > + > +A CAN device MUST conform to the following normative statements: > + > +\begin{itemize} > +\item \ref{devicenormative:Device Types / CAN Device / Feature bits} I just noticed that this introduces[1] an undefined reference (there's no device normative section for feature bits.) I'd suggest to just drop this reference (I can do that as a simple editorial update); if we want to have an actual normative reference for feature bits, it should be done via an extra change on top. > +\item \ref{devicenormative:Device Types / CAN Device / Device Operation / CAN Message Transmission} > +\end{itemize} [1] Easy to miss, as the current 1.4 branch has a pre-existing undefined reference, which will go away once we finally can merge into the main branch again and have all that craziness go away after we manage to do the actual 1.3 release :/ --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org