From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: Parav Pandit <parav@nvidia.com>,
virtio-dev@lists.oasis-open.org, cohuck@redhat.com,
virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-dev] [PATCH v3 06/20] virtio-mem-balloon: Maintain mem balloon device spec in separate directory
Date: Wed, 11 Jan 2023 09:55:59 -0500 [thread overview]
Message-ID: <20230111095538-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <b95d3aab-21c0-8256-a8bd-09e5b45cd206@redhat.com>
On Wed, Jan 11, 2023 at 03:14:10PM +0100, David Hildenbrand wrote:
> On 11.01.23 00:03, Parav Pandit wrote:
> > Move virtio memory balloon device specification to its own file
> > similar to recent virtio devices.
> > While at it, 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>
> >
>
> There is virtio-mem and there is virtio-balloon. Calling virtio-balloon
> "virtio-mem-balloon" can easily lead to quite some confusion. Any particular
> reason why not to stick to "virtio-balloon" ?
Yea, virtio-balloon scans better.
> --
> Thanks,
>
> David / dhildenb
next prev parent reply other threads:[~2023-01-11 14:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 23:03 [PATCH v3 00/20] Split device spec to its individual files Parav Pandit
2023-01-10 23:03 ` [PATCH v3 01/20] virtio-network: Maintain network device spec in separate directory Parav Pandit
2023-01-10 23:03 ` [PATCH v3 02/20] virtio-network: Fix spelling errors Parav Pandit
2023-01-10 23:03 ` [PATCH v3 03/20] virtio-block: Maintain block device spec in separate directory Parav Pandit
2023-01-10 23:03 ` [PATCH v3 04/20] virtio-console: Maintain console " Parav Pandit
2023-01-10 23:03 ` [PATCH v3 05/20] virtio-entropy: Maintain entropy " Parav Pandit
2023-01-10 23:03 ` [PATCH v3 06/20] virtio-mem-balloon: Maintain mem balloon " Parav Pandit
2023-01-11 14:14 ` [virtio-dev] " David Hildenbrand
2023-01-11 14:55 ` Michael S. Tsirkin [this message]
2023-01-11 15:01 ` Parav Pandit
2023-01-11 15:42 ` David Hildenbrand
2023-01-11 15:56 ` [virtio-comment] " Cornelia Huck
2023-01-11 16:01 ` Parav Pandit
2023-01-11 16:22 ` Michael S. Tsirkin
2023-01-11 16:32 ` Parav Pandit
2023-01-10 23:03 ` [PATCH v3 07/20] virtio-scsi: Maintain scsi host " Parav Pandit
2023-01-10 23:03 ` [PATCH v3 08/20] virtio-gpu: Maintain gpu " Parav Pandit
2023-01-10 23:03 ` [PATCH v3 09/20] virtio-input: Maintain input " Parav Pandit
2023-01-10 23:03 ` [PATCH v3 10/20] virtio-crypto: Maintain crypto " Parav Pandit
2023-01-10 23:03 ` [PATCH v3 11/20] virtio-vsock: Maintain socket " Parav Pandit
2023-01-11 11:04 ` [virtio-comment] " Cornelia Huck
2023-01-10 23:03 ` [PATCH v3 12/20] virtio-fs: Maintain file system " Parav Pandit
2023-01-10 23:03 ` [PATCH v3 13/20] virtio-rpmb: Maintain rpmb " Parav Pandit
2023-01-10 23:03 ` [PATCH v3 14/20] virtio-iommu: Maintain iommu " Parav Pandit
2023-01-10 23:03 ` [PATCH v3 15/20] virtio-sound: Maintain sound " Parav Pandit
2023-01-10 23:03 ` [PATCH v3 16/20] virtio-mem: Maintain memory " Parav Pandit
2023-01-10 23:03 ` [PATCH v3 17/20] virtio-i2c: Maintain i2c " Parav Pandit
2023-01-10 23:03 ` [PATCH v3 18/20] virtio-scmi: Maintain scmi " Parav Pandit
2023-01-10 23:03 ` [PATCH v3 19/20] virtio-gpio: Maintain gpio " Parav Pandit
2023-01-11 10:52 ` [virtio-dev] " Cornelia Huck
2023-01-11 13:40 ` [virtio-comment] " Parav Pandit
2023-01-10 23:03 ` [PATCH v3 20/20] virtio-pmem: Maintain pmem " Parav Pandit
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=20230111095538-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=david@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