From: David Marchand <david.marchand@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev <dev@dpdk.org>, "Xia, Chenbo" <chenbo.xia@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH 1/2] vhost: remove unneeded max enums
Date: Fri, 6 May 2022 09:12:01 +0200 [thread overview]
Message-ID: <CAJFAV8zGg2Ljf2gGij=0+VYD5MmA=_e7paWf9btnV+999rtdkg@mail.gmail.com> (raw)
In-Reply-To: <a8e02b5a-67b8-9a8b-f675-ba60673d3299@redhat.com>
On Thu, May 5, 2022 at 9:58 PM Maxime Coquelin
<maxime.coquelin@redhat.com> wrote:
> On 4/25/22 14:54, David Marchand wrote:
> > Move message handler description and callbacks into a single array and
> > remove unneeded VHOST_USER_MAX and VHOST_SLAVE_MAX enums.
> >
> > Signed-off-by: David Marchand <david.marchand@redhat.com>
> > ---
> > drivers/net/virtio/virtio_user/vhost_user.c | 1 -
> > examples/vhost_blk/blk_spec.h | 1 -
> > lib/vhost/vhost_user.c | 175 +++++++++-----------
> > lib/vhost/vhost_user.h | 2 -
> > 4 files changed, 76 insertions(+), 103 deletions(-)
> >
>
>
> Applied to dpdk-next-virtio/main without changing the commit title.
> Feel free to change it while pulling if you feel this is relevant.
This bad title probably comes from a time when the patch was indeed
only touching max enums.
Your suggestion is ok.
This will be fixed when pulling, thanks.
--
David Marchand
prev parent reply other threads:[~2022-05-06 7:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 12:54 David Marchand
2022-04-25 12:54 ` [PATCH 2/2] vhost: validate fds attached to messages David Marchand
2022-05-05 14:31 ` Maxime Coquelin
2022-05-05 19:58 ` Maxime Coquelin
2022-05-05 14:22 ` [PATCH 1/2] vhost: remove unneeded max enums Maxime Coquelin
2022-05-05 19:57 ` Maxime Coquelin
2022-05-06 7:12 ` David Marchand [this message]
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='CAJFAV8zGg2Ljf2gGij=0+VYD5MmA=_e7paWf9btnV+999rtdkg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=thomas@monjalon.net \
/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).