From: Kiran Kumar Kokkilagadda <kirankumark@marvell.com>
To: Huichao Cai <chcchc88@163.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
"yanzhirun_163@163.com" <yanzhirun_163@163.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: Re:RE: Re:RE: Re:RE: [EXTERNAL] [PATCH] test/graph: fix graph autotest second test failure
Date: Mon, 28 Oct 2024 09:48:15 +0000 [thread overview]
Message-ID: <SJ0PR18MB50536650A8EEBFE539E143A5AC4A2@SJ0PR18MB5053.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1c988134.9df4.192c3039155.Coremail.chcchc88@163.com>
> -----Original Message-----
> From: Huichao Cai <chcchc88@163.com>
> Sent: Friday, October 25, 2024 3:01 PM
> To: Kiran Kumar Kokkilagadda <kirankumark@marvell.com>
> Cc: Jerin Jacob <jerinj@marvell.com>; Nithin Kumar Dabilpuram
> <ndabilpuram@marvell.com>; yanzhirun_163@163.com; dev@dpdk.org
> Subject: Re:RE: Re:RE: Re:RE: [EXTERNAL] [PATCH] test/graph: fix graph
> autotest second test failure
>
> >We can fix this node id issue also. Something similar to this has been
> >fixed for graph id >Recently. We can do the same thing for node id as
> >well. >https: //patches. dpdk. org/project/dpdk/patch/20240618092324.
> >54166-2-rjarry@ redhat. com/
>
>
> >We can fix this node id issue also. Something similar to this has been
> >fixed for graph id
>
> >Recently. We can do the same thing for node id as well.
> >https://patches.dpdk.org/project/dpdk/patch/20240618092324.54166-2-
> rjar
> >ry@redhat.com/
> <https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__patches.dpdk.org_project_dpdk_patch_20240618092324.54166-2D2-
> 2Drjarry-
> 40redhat.com_&d=DwMGbg&c=nKjWec2b6R0mOyPaz7xtfQ&r=owEKckYY4F
> Tmil1Z6oBURwkTThyuRbLAY9LdfiaT6HA&m=N5-
> YM0oCO9qVUeRP5PqmCAjW9r9TbYSfnXQ8l906YZtptnm-QEfFtR-
> OBexfJrCS&s=BXf1fzz1sKd-xvzRjpjEjVrnxPKyhu-Plzk0I90s0XI&e=>
>
> So will you be able to complete this change in the near future?
I Will send a patch sometime next week.
prev parent reply other threads:[~2024-10-28 9:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 11:28 Huichao cai
2024-10-22 13:38 ` [EXTERNAL] " Kiran Kumar Kokkilagadda
2024-10-23 2:44 ` Huichao Cai
2024-10-23 12:42 ` Kiran Kumar Kokkilagadda
2024-10-24 6:46 ` Huichao Cai
2024-10-25 8:38 ` Kiran Kumar Kokkilagadda
2024-10-25 9:30 ` Huichao Cai
2024-10-28 9:48 ` Kiran Kumar Kokkilagadda [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=SJ0PR18MB50536650A8EEBFE539E143A5AC4A2@SJ0PR18MB5053.namprd18.prod.outlook.com \
--to=kirankumark@marvell.com \
--cc=chcchc88@163.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=yanzhirun_163@163.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).