All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Chaoyong He <chaoyong.he@corigine.com>
Cc: dev@dpdk.org, oss-drivers@corigine.com,
	niklas.soderlund@corigine.com,
	Peng Zhang <peng.zhang@corigine.com>,
	stable@dpdk.org
Subject: Re: [PATCH v1] buildtools: ensure the NUMA nodes are counted correct
Date: Mon, 29 Aug 2022 12:41:32 +0200	[thread overview]
Message-ID: <3248176.KgjxqYA5nG@thomas> (raw)
In-Reply-To: <1659426855-11014-1-git-send-email-chaoyong.he@corigine.com>

02/08/2022 09:54, Chaoyong He:
> From: Peng Zhang <peng.zhang@corigine.com>
> 
> Sorting a list of strings with the format "node[0-9]+" in order to find the
> largest integer by looking at the last item after the sort breaks. But if
> there are more then 10 items as a string sort will sort "node10" before
> "node2", it will get the error NUMA nodes.

What is the error you are seeing?




  reply	other threads:[~2022-08-29 10:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02  7:54 [PATCH v1] buildtools: ensure the NUMA nodes are counted correct Chaoyong He
2022-08-29 10:41 ` Thomas Monjalon [this message]
     [not found]   ` <MWHPR1301MB1997EA5A5CF4A320A13493E4EF769@MWHPR1301MB1997.namprd13.prod.outlook.com>
     [not found]     ` <3155813.0WQXIW03uk@thomas>
     [not found]       ` <MWHPR1301MB1997910EB07FA86DE33053C2EF799@MWHPR1301MB1997.namprd13.prod.outlook.com>
2022-08-31  8:47         ` FW: " Nole Zhang
2022-09-20 10:11           ` Niklas Soderlund
2022-09-20 13:22             ` Thomas Monjalon
2022-09-21  7:19               ` Nole Zhang
2022-09-21  8:07                 ` Thomas Monjalon
2022-09-22  8:06 ` [PATCH v2] " Niklas Söderlund
2022-10-10  7:52   ` Niklas Söderlund
2022-10-10 23:11   ` Thomas Monjalon

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=3248176.KgjxqYA5nG@thomas \
    --to=thomas@monjalon.net \
    --cc=chaoyong.he@corigine.com \
    --cc=dev@dpdk.org \
    --cc=niklas.soderlund@corigine.com \
    --cc=oss-drivers@corigine.com \
    --cc=peng.zhang@corigine.com \
    --cc=stable@dpdk.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.