From: David Hildenbrand <david@redhat.com>
To: Alok Tiwari <alok.a.tiwari@oracle.com>,
mst@redhat.com, jasowang@redhat.com, xuanzhuo@linux.alibaba.com,
eperezma@redhat.com, virtualization@lists.linux.dev
Cc: linux-kernel@vger.kernel.org, darren.kenny@oracle.com
Subject: Re: [PATCH 2/3] virtio-mem: fix multiple typos in struct comments and function docs
Date: Tue, 27 May 2025 21:12:20 +0200 [thread overview]
Message-ID: <ad77ace7-89e6-4b26-bd11-9b7ce176dde9@redhat.com> (raw)
In-Reply-To: <20250527183407.2093374-2-alok.a.tiwari@oracle.com>
> /*
> * Test if we could add memory without creating too much offline memory -
> - * to avoid running OOM if memory is getting onlined deferred.
> + * to avoid running OOM if memory is getting online deferred.
The system/user is onlining the memory, so the memory is getting "onlined"?
If it would be "getting online", wouldn't the memory start using the
internet or sth. like that? :D
> */
> static bool virtio_mem_could_add_memory(struct virtio_mem *vm, uint64_t size)
> {
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-05-27 19:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 18:33 [PATCH 1/3] virtio: Fix typo in register_virtio_device() doc comment Alok Tiwari
2025-05-27 18:33 ` [PATCH 2/3] virtio-mem: fix multiple typos in struct comments and function docs Alok Tiwari
2025-05-27 19:12 ` David Hildenbrand [this message]
2025-05-27 19:22 ` [External] : " ALOK TIWARI
2025-05-27 18:33 ` [PATCH 3/3] virtio_ring: Fix typos in comments and documentation Alok Tiwari
2025-05-29 6:02 ` [PATCH 1/3] virtio: Fix typo in register_virtio_device() doc comment Jason Wang
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=ad77ace7-89e6-4b26-bd11-9b7ce176dde9@redhat.com \
--to=david@redhat.com \
--cc=alok.a.tiwari@oracle.com \
--cc=darren.kenny@oracle.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.com \
/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
all inboxes | Powered by JetHome®