DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Varghese, Vipin" <Vipin.Varghese@amd.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"fengchengwen@huawei.com" <fengchengwen@huawei.com>,
	"konstantin.ananyev@huawei.com" <konstantin.ananyev@huawei.com>,
	"Yigit, Ferruh" <Ferruh.Yigit@amd.com>,
	"neerav.parikh@amd.com" <neerav.parikh@amd.com>
Subject: RE: [PATCH v3] app/dma-perf: calrify incorrect NUMA config
Date: Wed, 20 Nov 2024 17:42:44 +0000	[thread overview]
Message-ID: <PH7PR12MB859615D5A9F5040898E4376882212@PH7PR12MB8596.namprd12.prod.outlook.com> (raw)
In-Reply-To: <6103803.UjTJXf6HLC@thomas>

> 
> 20/03/2024 02:40, Vipin Varghese:
> > In case incorrect NUMA configuration, the current commit shares
> >  1) either `source or destination numa is greater`
> >  2) instead of `actual NUMA` it is `acture NUMA`
> >  3) uses `printf` instead of PRINT_ERR
> >
> > current patch changes the above to
> >  1) identify if source or|and destination is incorrect
> >  2) fix wording to incorrect
> >  3) use PRINT_ERR macro
> >
> > Signed-off-by: Vipin Varghese <vipin.varghese@amd.com>
> 
> Applied, thanks.

Thanks

> 
> 


      reply	other threads:[~2024-11-20 17:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06 15:02 [PATCH] " Vipin Varghese
2024-03-07 13:19 ` fengchengwen
2024-03-07 16:06   ` Varghese, Vipin
2024-03-11  6:00 ` [PATCH v2] " Vipin Varghese
2024-03-12  2:10   ` fengchengwen
2024-03-12  3:48     ` Varghese, Vipin
2024-03-13  9:37       ` Konstantin Ananyev
2024-03-20  1:14       ` Varghese, Vipin
2024-03-20  1:40   ` [PATCH v3] " Vipin Varghese
2024-11-19 17:07     ` Thomas Monjalon
2024-11-19 17:56     ` [EXTERNAL] " Gowrishankar Muthukrishnan
2024-11-19 22:37     ` Thomas Monjalon
2024-11-20 17:42       ` Varghese, Vipin [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=PH7PR12MB859615D5A9F5040898E4376882212@PH7PR12MB8596.namprd12.prod.outlook.com \
    --to=vipin.varghese@amd.com \
    --cc=Ferruh.Yigit@amd.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=konstantin.ananyev@huawei.com \
    --cc=neerav.parikh@amd.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).