From: Stephen Hemminger <stephen@networkplumber.org>
To: Anurag Mandal <anurag.mandal@intel.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com,
aman.deep.singh@intel.com, stable@dpdk.org
Subject: Re: [PATCH] app/testpmd: fix incorrect function names in logs
Date: Tue, 2 Dec 2025 15:49:11 -0800 [thread overview]
Message-ID: <20251202154911.7b1a377c@phoenix.local> (raw)
In-Reply-To: <20251201100837.422764-1-anurag.mandal@intel.com>
On Mon, 1 Dec 2025 10:08:36 +0000
Anurag Mandal <anurag.mandal@intel.com> wrote:
> VLAN extend and tpid setting functions have wrong function names
> mentioned in the error logs causing confusion as functions are
> not found in code using those names.
>
> Replaced static names with dynamic "__func__" predefined identifier.
>
> Fixes: 61a3b0e5e79f ("app/testpmd: send failure logs to stderr")
> Cc: stable@dpdk.org
>
> Signed-off-by: Anurag Mandal <anurag.mandal@intel.com>
> ---
Queued to next-net for 26.03
prev parent reply other threads:[~2025-12-02 23:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 10:08 Anurag Mandal
2025-12-01 15:58 ` Patrick Robb
2025-12-02 23:49 ` Stephen Hemminger [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=20251202154911.7b1a377c@phoenix.local \
--to=stephen@networkplumber.org \
--cc=aman.deep.singh@intel.com \
--cc=anurag.mandal@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--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 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).