From: Stephen Hemminger <stephen@networkplumber.org>
To: Nicolas Chautru <nicolas.chautru@intel.com>
Cc: dev@dpdk.org, maxime.coquelin@redhat.com, hemant.agrawal@nxp.com,
hernan.vargas@intel.com
Subject: Re: [PATCH v2 3/3] baseband/acc: add internal logging
Date: Thu, 23 Jan 2025 15:24:25 -0800 [thread overview]
Message-ID: <20250123152425.0663a626@hermes.local> (raw)
In-Reply-To: <20250123225519.2469167-4-nicolas.chautru@intel.com>
On Thu, 23 Jan 2025 14:55:19 -0800
Nicolas Chautru <nicolas.chautru@intel.com> wrote:
> Adds internal buffer for more flexible logging.
>
> Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
Inventing another device specific error log seems like a short sighted concept.
Why doesn't existing DPDK logging work well enough?
prev parent reply other threads:[~2025-01-23 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 22:55 [PATCH v2 0/3] bbdev: trace point and logging Nicolas Chautru
2025-01-23 22:55 ` [PATCH v2 1/3] bbdev: add trace point Nicolas Chautru
2025-01-23 22:55 ` [PATCH v2 2/3] baseband/acc: " Nicolas Chautru
2025-01-23 22:55 ` [PATCH v2 3/3] baseband/acc: add internal logging Nicolas Chautru
2025-01-23 23:24 ` 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=20250123152425.0663a626@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=hernan.vargas@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=nicolas.chautru@intel.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).