Linux virtualization list
 help / color / mirror / Atom feed
From: xiongwm2026  <xiongwm2026@163.com>
To: "Parav Pandit" <parav@nvidia.com>
Cc: "mst@redhat.com" <mst@redhat.com>,
	"jasowangio@gmail.com" <jasowangio@gmail.com>,
	"david@redhat.com" <david@redhat.com>,
	"virtualization@lists.linux.dev" <virtualization@lists.linux.dev>,
	xiongweimin <xiongweimin@kylinos.cn>
Subject: Re:RE: [PATCH] virtio_mem: fix typo in comment
Date: Tue, 14 Jul 2026 14:00:29 +0800 (CST)	[thread overview]
Message-ID: <2f2e17ce.4699.19f5f366bfd.Coremail.xiongwm2026@163.com> (raw)
In-Reply-To: <SJ0PR12MB6806262FB6F99ADA13EC127CDCF92@SJ0PR12MB6806.namprd12.prod.outlook.com>



Hi Parav,

Thanks for the review!

Best regards,
Weimin

At 2026-07-14 12:27:45, "Parav Pandit" <parav@nvidia.com> wrote:
>
>
>> From: weimin xiong <xiongwm2026@163.com>
>> Sent: 14 July 2026 08:54 AM
>> 
>> [You don't often get email from xiongwm2026@163.com. Learn why this is important at
>> https://aka.ms/LearnAboutSenderIdentification ]
>
>> 
>> From: xiongweimin <xiongweimin@kylinos.cn>
>> 
>> Correct "actipn" to "action".
>> 
>> Signed-off-by: xiongweimin <xiongweimin@kylinos.cn>
>> ---
>>  drivers/virtio/virtio_mem.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>> 
>> diff --git a/drivers/virtio/virtio_mem.c b/drivers/virtio/virtio_mem.c
>> index 11c441501..90d8ef0b9 100644
>> --- a/drivers/virtio/virtio_mem.c
>> +++ b/drivers/virtio/virtio_mem.c
>> @@ -1080,7 +1080,7 @@ static int virtio_mem_memory_notifier_cb(struct notifier_block *nb,
>>                 atomic64_sub(size, &vm->offline_size);
>>                 /*
>>                  * Start adding more memory once we onlined half of our
>> -                * threshold. Don't trigger if it's possibly due to our actipn
>> +                * threshold. Don't trigger if it's possibly due to our action
>>                  * (e.g., us adding memory which gets onlined immediately from
>>                  * the core).
>>                  */
>> --
>> 2.43.0
>> 
>> 
>> No virus found
>>                 Checked by Hillstone Network AntiVirus
>> 
>
>Reviewed-by: Parav Pandit <parav@nvidia.com>

  reply	other threads:[~2026-07-14  6:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14  3:24 [PATCH] virtio_mem: fix typo in comment weimin xiong
2026-07-14  4:27 ` Parav Pandit
2026-07-14  6:00   ` xiongwm2026 [this message]
2026-07-14  8:44 ` David Hildenbrand (Arm)

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=2f2e17ce.4699.19f5f366bfd.Coremail.xiongwm2026@163.com \
    --to=xiongwm2026@163.com \
    --cc=david@redhat.com \
    --cc=jasowangio@gmail.com \
    --cc=mst@redhat.com \
    --cc=parav@nvidia.com \
    --cc=virtualization@lists.linux.dev \
    --cc=xiongweimin@kylinos.cn \
    /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