From: David Marchand <david.marchand@redhat.com>
To: Long Li <longli@microsoft.com>
Cc: "wenxuanx.wu@intel.com" <wenxuanx.wu@intel.com>,
"qiming.yang@intel.com" <qiming.yang@intel.com>,
"qi.z.zhang@intel.com" <qi.z.zhang@intel.com>,
"nhorman@tuxdriver.com" <nhorman@tuxdriver.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH] eal/linux: fix fail to stop device monitor error
Date: Wed, 16 Feb 2022 11:01:09 +0100 [thread overview]
Message-ID: <CAJFAV8zLWHuAA1Ch+QjrXKNiYOENu9AuSHtyOEWS0C3+RB_J-Q@mail.gmail.com> (raw)
In-Reply-To: <BY5PR21MB15066D62F846C420CF87B29DCE359@BY5PR21MB1506.namprd21.prod.outlook.com>
On Wed, Feb 16, 2022 at 9:10 AM Long Li <longli@microsoft.com> wrote:
>
> > Subject: [PATCH] eal/linux: fix fail to stop device monitor error
> >
> > [You don't often get email from wenxuanx.wu@intel.com. Learn why this is
> > important at http://aka.ms/LearnAboutSenderIdentification.]
> >
> > From: Wenxuan Wu <wenxuanx.wu@intel.com>
> >
> > The ret value stands for whether the device monitor has been successfully
> > closed, and has nothing to do with rte_intr_callback_unregister funcs once it
> > return a value greater than 0 .So if the closure procedure has gone to the
> > right exit point ,we should set this value to 0.
>
> It seems to be a display problem with the patch in this email.
There is no issue with displaying.
The proposed patch can be found in patchwork under:
https://patchwork.dpdk.org/project/dpdk/patch/20220211065315.66814-1-wenxuanx.wu@intel.com/
>
> But the patch at https://patchwork.dpdk.org/project/dpdk/patch/20220211084131.72606-1-wenxuanx.wu@intel.com/ looks good to me.
The patch you reference is in another mail thread you can find from
patchwork (see "mailing list archive" link in patch):
https://inbox.dpdk.org/dev/20220211084131.72606-1-wenxuanx.wu@intel.com/
--
David Marchand
prev parent reply other threads:[~2022-02-16 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 6:53 wenxuanx.wu
2022-02-16 8:10 ` Long Li
2022-02-16 10:01 ` 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=CAJFAV8zLWHuAA1Ch+QjrXKNiYOENu9AuSHtyOEWS0C3+RB_J-Q@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=longli@microsoft.com \
--cc=nhorman@tuxdriver.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=wenxuanx.wu@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).