From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Nicolas Chautru <nicolas.chautru@intel.com>, dev@dpdk.org
Cc: hemant.agrawal@nxp.com, hernan.vargas@intel.com
Subject: Re: [PATCH v2 2/3] baseband/acc: add trace point
Date: Tue, 4 Mar 2025 16:11:58 +0100 [thread overview]
Message-ID: <a818ab9e-ceb0-45a9-a410-6f394e8a9f29@redhat.com> (raw)
In-Reply-To: <20250123225519.2469167-3-nicolas.chautru@intel.com>
On 1/23/25 11:55 PM, Nicolas Chautru wrote:
> Improvement of logging to notably use trace point
> for driver specific error logging and tracepoint.
>
> Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
> ---
> drivers/baseband/acc/acc_common.c | 8 ++++
> drivers/baseband/acc/acc_common.h | 55 ++++++++++++++++++++++++++
> drivers/baseband/acc/rte_vrb_pmd.c | 63 +++++++++++++++++-------------
> drivers/baseband/acc/vrb_trace.h | 35 +++++++++++++++++
> 4 files changed, 133 insertions(+), 28 deletions(-)
> create mode 100644 drivers/baseband/acc/vrb_trace.h
>
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Thanks,
Maxime
next prev parent reply other threads:[~2025-03-04 15:12 UTC|newest]
Thread overview: 15+ 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-02-07 8:40 ` Maxime Coquelin
2025-01-23 22:55 ` [PATCH v2 2/3] baseband/acc: " Nicolas Chautru
2025-03-04 15:11 ` Maxime Coquelin [this message]
2025-01-23 22:55 ` [PATCH v2 3/3] baseband/acc: add internal logging Nicolas Chautru
2025-01-23 23:24 ` Stephen Hemminger
2025-01-24 17:52 ` Chautru, Nicolas
2025-01-24 18:00 ` Stephen Hemminger
2025-01-24 21:21 ` Chautru, Nicolas
2025-02-07 9:52 ` Maxime Coquelin
2025-02-28 8:51 ` Maxime Coquelin
2025-02-28 17:28 ` Chautru, Nicolas
2025-03-04 15:11 ` Maxime Coquelin
2025-03-04 21:03 ` [PATCH v2 0/3] bbdev: trace point and logging Maxime Coquelin
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=a818ab9e-ceb0-45a9-a410-6f394e8a9f29@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=hernan.vargas@intel.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).