All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Chengwen Feng" <fengchengwen@huawei.com>, <thomas@monjalon.net>,
	<stephen@networkplumber.org>
Cc: <dev@dpdk.org>
Subject: RE: [PATCH 0/2] enhance telemetry list endpoint with device name
Date: Wed, 20 May 2026 07:40:02 +0200	[thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35F65885@smartserver.smartshare.dk> (raw)
In-Reply-To: <20260520035641.50555-1-fengchengwen@huawei.com>

> From: Chengwen Feng [mailto:fengchengwen@huawei.com]
> Sent: Wednesday, 20 May 2026 05.57
> 
> Currently, the /dmadev/list and /ethdev/list telemetry endpoints return
> only integer IDs, making it hard to identify devices. This series
> changes
> both to output strings in "ID    NAME" format for better usability.

For machine reading of the JSON output, it would be better returning an object with an integer and a string field, {ID, "NAME"}.


  parent reply	other threads:[~2026-05-20  5:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-20  3:56 [PATCH 0/2] enhance telemetry list endpoint with device name Chengwen Feng
2026-05-20  3:56 ` [PATCH 1/2] dmadev: include device name in telemetry list output Chengwen Feng
2026-05-20 15:03   ` Stephen Hemminger
2026-05-20  3:56 ` [PATCH 2/2] ethdev: " Chengwen Feng
2026-05-20  5:40 ` Morten Brørup [this message]
2026-05-20  7:31   ` [PATCH 0/2] enhance telemetry list endpoint with device name fengchengwen
2026-05-20  7:49     ` Bruce Richardson
2026-05-20 14:54       ` Stephen Hemminger
2026-05-20  9:38 ` [PATCH v2 0/2] Add list names telemetry endpoint Chengwen Feng
2026-05-20  9:38   ` [PATCH v2 1/2] dmadev: add telemetry endpoint for list names Chengwen Feng
2026-05-20  9:38   ` [PATCH v2 2/2] ethdev: " Chengwen Feng
2026-05-20 13:29     ` Morten Brørup
2026-05-20 14:58       ` Bruce Richardson
2026-05-21 12:24         ` fengchengwen
2026-05-21 12:40           ` Morten Brørup
2026-05-21 14:37             ` Stephen Hemminger
2026-05-21 15:21               ` Bruce Richardson
2026-05-21 15:44                 ` Bruce Richardson
2026-05-22  0:42                   ` fengchengwen

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=98CBD80474FA8B44BF855DF32C47DC35F65885@smartserver.smartshare.dk \
    --to=mb@smartsharesystems.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=stephen@networkplumber.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 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.