From: "Guo, Junfeng" <junfeng.guo@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
"Wu, Jingjing" <jingjing.wu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] raw/ntb: add check for DB intr handler registering
Date: Tue, 8 Mar 2022 08:11:56 +0000 [thread overview]
Message-ID: <DM6PR11MB37239F44243ED34740F62774E7099@DM6PR11MB3723.namprd11.prod.outlook.com> (raw)
In-Reply-To: <4436666.BjyWNHgNrj@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Tuesday, March 8, 2022 16:10
> To: Wu, Jingjing <jingjing.wu@intel.com>; Guo, Junfeng
> <junfeng.guo@intel.com>
> Cc: dev@dpdk.org; stable@dpdk.org
> Subject: Re: [PATCH] raw/ntb: add check for DB intr handler registering
>
> 08/03/2022 09:08, Guo, Junfeng:
> > From: Thomas Monjalon <thomas@monjalon.net>
> > > There is no formal ack. What is the status of this patch?
> > >
> >
> > Thanks for the reminding!
> > Currently, we agreed that this fix is not for the root cause of no
> response of doorbell
> > interrupt when building the connection between two NTB ports. So we
> decided to
> > change the status to be superseded and do further investigation for NTB.
> > Thanks for the reviewing!
>
> In this case, it should not be superseded but rejected.
>
Sure, thanks for your comment!
>
prev parent reply other threads:[~2022-03-08 8:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 6:28 Junfeng Guo
2022-02-10 7:04 ` Wu, Jingjing
2022-02-10 7:18 ` Guo, Junfeng
2022-02-10 10:43 ` Guo, Junfeng
2022-03-07 17:07 ` Thomas Monjalon
2022-03-08 8:08 ` Guo, Junfeng
2022-03-08 8:09 ` Thomas Monjalon
2022-03-08 8:11 ` Guo, Junfeng [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=DM6PR11MB37239F44243ED34740F62774E7099@DM6PR11MB3723.namprd11.prod.outlook.com \
--to=junfeng.guo@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=stable@dpdk.org \
--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).