From: David Marchand <david.marchand@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, yux.jiang@intel.com, chenbox@nvidia.com
Subject: Re: [PATCH] vhost: fix FD registration to the fdset
Date: Mon, 17 Jun 2024 16:25:02 +0200 [thread overview]
Message-ID: <CAJFAV8yHgsFw+_gSAzf1BMx1Ua-LGtD-JWt80E8i0NaW6XXYHg@mail.gmail.com> (raw)
In-Reply-To: <20240617101334.211756-1-maxime.coquelin@redhat.com>
On Mon, Jun 17, 2024 at 12:13 PM Maxime Coquelin
<maxime.coquelin@redhat.com> wrote:
>
> A missing return statement in fdset_add() was making
> the error path to be systematically executed, this patch
> adds it back.
>
> Bugzilla ID: 1462
> Fixes: 0e38b42bf61c ("vhost: manage FD with epoll")
It looks like the initial code was better ;-).
>
> Reported-by: Jiang Yu <yux.jiang@intel.com>
> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Reviewed-by: David Marchand <david.marchand@redhat.com>
Applied directly in main for rc1, thanks.
--
David Marchand
prev parent reply other threads:[~2024-06-17 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 10:13 Maxime Coquelin
2024-06-17 14:25 ` 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=CAJFAV8yHgsFw+_gSAzf1BMx1Ua-LGtD-JWt80E8i0NaW6XXYHg@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=chenbox@nvidia.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=yux.jiang@intel.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).