From: "Bathija, Pravin" <Pravin.Bathija@dell.com>
To: fengchengwen <fengchengwen@huawei.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "pravin.m.bathija.dev@gmail.com" <pravin.m.bathija.dev@gmail.com>
Subject: RE: [PATCH v3 1/5] vhost: add user to mailmap and define to vhost hdr
Date: Tue, 11 Nov 2025 11:14:44 +0000 [thread overview]
Message-ID: <SJ0PR19MB460673D899237DEFC7861179F5CFA@SJ0PR19MB4606.namprd19.prod.outlook.com> (raw)
In-Reply-To: <ae3c917c-42f0-4764-836a-292cd89b7a53@huawei.com>
Responses inline.
Internal Use - Confidential
> -----Original Message-----
> From: fengchengwen <fengchengwen@huawei.com>
> Sent: Monday, November 3, 2025 11:15 PM
> To: Bathija, Pravin <Pravin.Bathija@dell.com>; dev@dpdk.org
> Cc: pravin.m.bathija.dev@gmail.com
> Subject: Re: [PATCH v3 1/5] vhost: add user to mailmap and define to vhost hdr
>
>
> [EXTERNAL EMAIL]
>
> Please fix a typo below
> Acked-by: Chengwen Feng <fengchengwen@huawei.com>
>
> On 11/4/2025 12:21 PM, Pravin M Bathija wrote:
> > - add user to mailmap fle
> > - define a bit-field called
> VHOST_USER_PROTOCOL_F_CONFIGURE_MEM_SLOTS
> > that depicts if the fature/capability to add/remove memory regions is
>
> fature -> feature
Made the change as suggested in latest patch v4.
>
> > supported. This is a part of the overall support for add/remove memory
> > region feature in this patchset.
> >
> > Signed-off-by: Pravin M Bathija <pravin.bathija@dell.com>
next prev parent reply other threads:[~2025-11-11 11:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 4:21 [PATCH v3 0/5] Support add/remove memory region & get-max-slots Pravin M Bathija
2025-11-04 4:21 ` [PATCH v3 1/5] vhost: add user to mailmap and define to vhost hdr Pravin M Bathija
2025-11-04 7:15 ` fengchengwen
2025-11-11 11:14 ` Bathija, Pravin [this message]
2025-11-04 4:21 ` [PATCH v3 2/5] vhost_user: header defines for add/rem mem region Pravin M Bathija
2025-11-04 7:18 ` fengchengwen
2025-11-04 4:21 ` [PATCH v3 3/5] vhost_user: Function defs for add/rem mem regions Pravin M Bathija
2025-11-04 7:48 ` fengchengwen
2025-11-11 11:28 ` Bathija, Pravin
2025-11-04 4:21 ` [PATCH v3 4/5] vhost_user: support function defines for back-end Pravin M Bathija
2025-11-04 8:05 ` fengchengwen
2025-11-11 11:31 ` Bathija, Pravin
2025-11-12 1:21 ` fengchengwen
2025-11-04 4:21 ` [PATCH v3 5/5] vhost_user: Increase number of memory regions Pravin M Bathija
2025-11-04 8:12 ` fengchengwen
2025-11-11 11:34 ` Bathija, Pravin
2025-11-12 1:26 ` fengchengwen
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=SJ0PR19MB460673D899237DEFC7861179F5CFA@SJ0PR19MB4606.namprd19.prod.outlook.com \
--to=pravin.bathija@dell.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=pravin.m.bathija.dev@gmail.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;
as well as URLs for NNTP newsgroup(s).