From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: virtio-comment@lists.linux.dev, cohuck@redhat.com
Subject: Re: [PULL v4 ] administration commands for device parts
Date: Sun, 14 Jul 2024 11:50:56 -0400 [thread overview]
Message-ID: <20240714115023-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20240714150028.3292710-1-parav@vr-arch-host06.mtvr.labs.mlnx>
On Sun, Jul 14, 2024 at 03:01:07PM +0000, Parav Pandit wrote:
> From: Parav Pandit <parav@nvidia.com>
>
> Hi Michael, Cornelia,
>
> The following changes since commit 9b3129fe72360a78e76b6dd890d3abc5a45fa915:
>
> virtio_pci_cap64: specify offset_hi, length_hi endianness (2024-07-12 06:43:53 -0400)
>
> are available in the Git repository at:
>
> https://github.com/paravmellanox/virtio-spec.git tags/for_1.4_v4
>
> for you to fetch changes up to f89c2818bba1bd0d80bb12372973deb6908931f2:
>
> editorial: replace hyperref with ref (2024-07-14 17:44:14 +0300)
>
> If the change f89c2818bba1bd0d80bb12372973deb6908931f2 still not reaches to your
> expected quality level, can you please pull upto 52d320c8b3c54ae035c0ddc1d23ae997cbfa13b2?
> I will supply the requested improvements on top of virtio-1.4 branch on top of
> 52d320c8b3c54ae035c0ddc1d23ae997cbfa13b2 once merged.
>
> ----------------------------------------------------------------
> This tag contains administration commands for device parts
>
> changelog:
> v3->v4:
> - addressed Michael's comment to add fixes tag to the patches
> in editorial patch
> v2->v3:
> - added message-id to the last patch
> - fixed reference to named reference in the last patch
> v1->v2:
> - fixed hyper reference to name reference
> - fixed typo in commit log
> - reduced the patches of pull request due to rebase of virtio-1.4 branch
> v0->v1:
> - resolved merge conflict for an empty line in newdevice.tex
>
>
> ----------------------------------------------------------------
> Parav Pandit (6):
> admin: Add theory of operation for device parts
> admin: Extend resource objects for sr-iov group type
> admin: Add admin commands for device parts
> admin: Define common device parts
> admin: Add requirements of device parts commands
> editorial: replace hyperref with ref
>
> admin-cmds-capabilities.tex | 16 ++
> admin-cmds-device-parts.tex | 469 ++++++++++++++++++++++++++++++++++++++++
> admin-cmds-resource-objects.tex | 29 ++-
> admin.tex | 12 +-
> conformance.tex | 2 +
> content.tex | 1 +
> device-parts.tex | 232 ++++++++++++++++++++
> newdevice.tex | 24 +-
> 8 files changed, 778 insertions(+), 7 deletions(-)
> create mode 100644 admin-cmds-device-parts.tex
> create mode 100644 device-parts.tex
Parav, makediff fails. Did you, in fact, run make diff and
inspect the changes?
Because it's not really practical to review the whole document
each time ...
--
MST
next prev parent reply other threads:[~2024-07-14 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-14 15:01 [PULL v4 ] administration commands for device parts Parav Pandit
2024-07-14 15:50 ` Michael S. Tsirkin [this message]
2024-07-14 22:20 ` Parav Pandit
2024-07-15 8:52 ` Cornelia Huck
2024-07-15 8:56 ` Michael S. Tsirkin
2024-07-15 10:08 ` Michael S. Tsirkin
2024-07-15 11:12 ` Cornelia Huck
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=20240714115023-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=parav@nvidia.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox