Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Parav Pandit <parav@nvidia.com>,
	virtio-dev@lists.oasis-open.org,
	virtio-comment@lists.oasis-open.org
Subject: [virtio-dev] Re: [virtio-comment] [PATCH v1 13/20] virtio-rpmb: Maintain rpmb device spec in separate directory
Date: Mon, 09 Jan 2023 14:47:14 +0100	[thread overview]
Message-ID: <87sfgjddlp.fsf@redhat.com> (raw)
In-Reply-To: <20230109083413-mutt-send-email-mst@kernel.org>

On Mon, Jan 09 2023, "Michael S. Tsirkin" <mst@redhat.com> wrote:

> On Mon, Jan 09, 2023 at 01:48:27PM +0100, Cornelia Huck wrote:
>> On Sun, Jan 01 2023, Parav Pandit <parav@nvidia.com> wrote:
>> 
>> > Place device specification, its driver and device
>> > conformance into its own directory to have self contained device
>> > specification.
>> >
>> > Fixes: https://github.com/oasis-tcs/virtio-spec/issues/153
>> > Signed-off-by: Parav Pandit <parav@nvidia.com>
>> > ---
>> > changelog:
>> > v0->v1:
>> > - new patch
>> > ---
>> >  conformance.tex                               | 23 ++-----------------
>> >  content.tex                                   |  1 -
>> >  .../virtio-rpmb/device-conformance.tex        | 13 +++++++++++
>> >  .../virtio-rpmb/device.tex                    |  0
>> >  .../virtio-rpmb/driver-conformance.tex        |  7 ++++++
>> >  5 files changed, 22 insertions(+), 22 deletions(-)
>> >  create mode 100644 device-types/virtio-rpmb/device-conformance.tex
>> >  rename virtio-rpmb.tex => device-types/virtio-rpmb/device.tex (100%)
>> >  create mode 100644 device-types/virtio-rpmb/driver-conformance.tex
>> >
>> 
>> (...)
>> 
>> > diff --git a/content.tex b/content.tex
>> > index a486e36..13a2a94 100644
>> > --- a/content.tex
>> > +++ b/content.tex
>> > @@ -3014,7 +3014,6 @@ \chapter{Device Types}\label{sec:Device Types}
>> >  \import{device-types/virtio-crypto/}{device}
>> >  \import{device-types/virtio-vsock/}{device}
>> >  \import{device-types/virtio-fs/}{device}
>> > -\input{virtio-rpmb.tex}
>> 
>> This is missing
>> 
>> \import{device-types/virtio-rpmb/}{device}
>> 
>> (I noticed broken references when building with the patches applied)
>
>
> Oh, good catch. Parav, I'd really like patch submitters to run the
> build and review the resulting files.
> I guess we should withdraw the ballot for now and wait until a fixed
> version. Agree?

Withdrawing the ballot sounds like the best option to me.

For a respin, it might also be a good idea to drop the extra blank line
before EOF for (IIRC) net and block that git am complained about.


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2023-01-09 13:47 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-01 18:08 [virtio-comment] [PATCH v1 00/20] Split device spec to its individual files Parav Pandit
2023-01-01 18:08 ` [virtio-dev] [PATCH v1 01/20] virtio-network: Maintain network device spec in separate directory Parav Pandit
2023-01-09 13:42   ` [virtio-comment] " Michael S. Tsirkin
2023-01-09 14:12     ` [virtio-comment] " Parav Pandit
2023-01-09 17:16       ` [virtio-dev] " Michael S. Tsirkin
2023-01-09 19:14       ` [virtio-comment] " Michael S. Tsirkin
2023-01-09 22:41         ` [virtio-comment] " Parav Pandit
2023-01-01 18:08 ` [virtio-comment] [PATCH v1 02/20] virtio-network: Fix spelling errors Parav Pandit
2023-01-01 18:08 ` [virtio-comment] [PATCH v1 03/20] virtio-block: Maintain block device spec in separate directory Parav Pandit
2023-01-01 18:08 ` [virtio-comment] [PATCH v1 04/20] virtio-console: Maintain console " Parav Pandit
2023-01-01 18:08 ` [virtio-dev] [PATCH v1 05/20] virtio-entropy: Maintain entropy " Parav Pandit
2023-01-01 18:08 ` [virtio-comment] [PATCH v1 06/20] virtio-mem-balloon: Maintain mem balloon " Parav Pandit
2023-01-01 18:08 ` [virtio-comment] [PATCH v1 07/20] virtio-scsi: Maintain scsi host " Parav Pandit
2023-01-01 18:08 ` [virtio-comment] [PATCH v1 08/20] virtio-gpu: Maintain gpu " Parav Pandit
2023-01-01 18:08 ` [virtio-comment] [PATCH v1 09/20] virtio-input: Maintain input " Parav Pandit
2023-01-01 18:08 ` [virtio-comment] [PATCH v1 10/20] virtio-crypto: Maintain crypto " Parav Pandit
2023-01-01 18:08 ` [virtio-comment] [PATCH v1 11/20] virtio-vsock: Maintain socket " Parav Pandit
2023-01-01 18:08 ` [virtio-comment] [PATCH v1 12/20] virtio-fs: Maintain file system " Parav Pandit
2023-01-01 18:08 ` [virtio-comment] [PATCH v1 13/20] virtio-rpmb: Maintain rpmb " Parav Pandit
2023-01-09 12:48   ` Cornelia Huck
2023-01-09 13:35     ` Michael S. Tsirkin
2023-01-09 13:47       ` Cornelia Huck [this message]
2023-01-09 13:53         ` [virtio-dev] " Cornelia Huck
2023-01-09 14:13         ` Parav Pandit
2023-01-09 14:08       ` Parav Pandit
2023-01-01 18:08 ` [virtio-comment] [PATCH v1 14/20] virtio-iommu: Maintain iommu " Parav Pandit
2023-01-01 18:08 ` [virtio-comment] [PATCH v1 15/20] virtio-sound: Maintain sound " Parav Pandit
2023-01-09 13:05   ` [virtio-dev] " Cornelia Huck
2023-01-01 18:08 ` [virtio-comment] [PATCH v1 16/20] virtio-mem: Maintain memory " Parav Pandit
2023-01-01 18:08 ` [virtio-comment] [PATCH v1 17/20] virtio-i2c: Maintain i2c " Parav Pandit
2023-01-09 13:07   ` [virtio-dev] " Cornelia Huck
2023-01-01 18:08 ` [virtio-comment] [PATCH v1 18/20] virtio-scmi: Maintain scmi " Parav Pandit
2023-01-01 18:08 ` [virtio-comment] [PATCH v1 19/20] virtio-gpio: Maintain gpio " Parav Pandit
2023-01-09 13:11   ` Cornelia Huck
2023-01-01 18:08 ` [virtio-comment] [PATCH v1 20/20] virtio-pmem: Maintain pmem " Parav Pandit
2023-01-03 10:47 ` [virtio-dev] Re: [PATCH v1 00/20] Split device spec to its individual files Michael S. Tsirkin
2023-01-03 14:15   ` [virtio-comment] " Parav Pandit
2023-01-03 14:19     ` [virtio-comment] " Michael S. Tsirkin
2023-01-03 14:26       ` [virtio-dev] " Parav Pandit
2023-01-03 15:43         ` [virtio-comment] " Michael S. Tsirkin
2023-01-03 16:04           ` [virtio-comment] " Parav Pandit
2023-01-03 16:19             ` [virtio-comment] " Michael S. Tsirkin
2023-01-03 16:41               ` [virtio-comment] " Parav Pandit
2023-01-03 16:52                 ` [virtio-dev] " Michael S. Tsirkin
2023-01-03 18:00                   ` [virtio-comment] " Parav Pandit
2023-01-03 11:01 ` [virtio-comment] " Michael S. Tsirkin

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=87sfgjddlp.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=mst@redhat.com \
    --cc=parav@nvidia.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio-dev@lists.oasis-open.org \
    /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