From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Bertrand Marquis <bertrand.marquis@arm.com>,
virtio-comment@lists.linux.dev
Cc: "Edgar E . Iglesias" <edgar.iglesias@amd.com>,
Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Alex Bennee <alex.bennee@linaro.org>,
Armelle Laine <armellel@google.com>,
Bill Mills <bill.mills@linaro.org>
Subject: Re: [PATCH v2 1/6] virtio-msg: add new command for bus normative
Date: Fri, 13 Nov 2026 14:28:32 +0100 [thread overview]
Message-ID: <ef8bfad9-8b56-4e5b-beff-d0111b3b03a6@kernel.org> (raw)
In-Reply-To: <998059c704fffafbceb9804045b9ffe6cf7a64b2.1781514628.git.bertrand.marquis@arm.com>
On 6/15/26 11:10, Bertrand Marquis wrote:
> Add a new command to have a standard way to define virtio-msg bus
> normative statements.
>
> Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com>
> Signed-off-by: Bill Mills <bill.mills@linaro.org>
> ---
> commands.tex | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/commands.tex b/commands.tex
> index 25ea8ee3bc78..122a97f89b10 100644
> --- a/commands.tex
> +++ b/commands.tex
> @@ -7,9 +7,10 @@
> % How we format a field name
> \newcommand{\field}[1]{\emph{#1}}
>
> -% Mark a normative section (driver or device)
> +% Mark a normative section (driver, device, or bus)
> \newcommand{\drivernormative}[3]{#1{Driver Requirements: #2}\label{drivernormative:#3}}
> \newcommand{\devicenormative}[3]{#1{Device Requirements: #2}\label{devicenormative:#3}}
> +\newcommand{\busnormative}[3]{#1{Bus Requirements: #2}\label{busnormative:#3}}
> \newcounter{clausecounter}
> \newcommand{\conformance}[2]{
> \stepcounter{clausecounter}
Reviewed-by: David Hildenbrand (Arm) <david@kernel.org>
--
Cheers,
David
next prev parent reply other threads:[~2026-11-13 13:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 9:10 [PATCH v2 0/6] virtio-msg transport layer Bertrand Marquis
2026-06-15 9:10 ` [PATCH v2 1/6] virtio-msg: add new command for bus normative Bertrand Marquis
2026-11-13 13:28 ` David Hildenbrand (Arm) [this message]
2026-06-15 9:10 ` [PATCH v2 2/6] virtio-msg: Add the FF-A bus bibliography reference Bertrand Marquis
2026-11-13 13:28 ` David Hildenbrand (Arm)
2026-06-15 9:10 ` [PATCH v2 3/6] virtio-msg: Add virtio-msg, a message based virtio transport layer Bertrand Marquis
2026-07-08 15:43 ` Michael Riesch
2026-11-13 15:29 ` David Hildenbrand (Arm)
2026-06-15 9:10 ` [PATCH v2 4/6] virtio-msg: link virtio-msg content Bertrand Marquis
2026-11-13 16:30 ` David Hildenbrand (Arm)
2026-06-15 9:10 ` [PATCH v2 5/6] virtio-msg: add conformance entries in conformance chapter Bertrand Marquis
2026-11-13 16:31 ` David Hildenbrand (Arm)
2026-06-15 9:10 ` [PATCH v2 6/6] virtio-msg: add message transport to core references Bertrand Marquis
2026-11-13 16:32 ` David Hildenbrand (Arm)
2026-07-01 15:20 ` [PATCH v2 0/6] virtio-msg transport layer Alex Bennée
2026-07-01 15:30 ` Parav Pandit
2026-07-01 22:19 ` Michael S. Tsirkin
2026-10-21 15:23 ` Alex Bennée
2026-10-21 15:42 ` Michael S. Tsirkin
2026-11-05 21:19 ` Ayrton Munoz
2026-09-01 15:24 ` Viresh Kumar
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=ef8bfad9-8b56-4e5b-beff-d0111b3b03a6@kernel.org \
--to=david@kernel.org \
--cc=alex.bennee@linaro.org \
--cc=armellel@google.com \
--cc=arnaud.pouliquen@foss.st.com \
--cc=bertrand.marquis@arm.com \
--cc=bill.mills@linaro.org \
--cc=edgar.iglesias@amd.com \
--cc=viresh.kumar@linaro.org \
--cc=virtio-comment@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.