From: David Marchand <david.marchand@redhat.com>
To: Gagandeep Singh <g.singh@nxp.com>
Cc: dev@dpdk.org, Hemant Agrawal <hemant.agrawal@nxp.com>,
Jun Yang <jun.yang@nxp.com>
Subject: Re: [v3] crypto/dpaa2_sec: rework debug code
Date: Thu, 10 Oct 2024 09:06:09 +0200 [thread overview]
Message-ID: <CAJFAV8yA1m5GyHQC=ucaqXrMRFUVe7KffeZAa-EeSkP44dL_gw@mail.gmail.com> (raw)
In-Reply-To: <20241010060300.2308647-1-g.singh@nxp.com>
On Thu, Oct 10, 2024 at 8:03 AM Gagandeep Singh <g.singh@nxp.com> wrote:
>
> Move the duplicate code in a common function and
> remove un-necessary newline characters from the logs.
>
> Signed-off-by: Jun Yang <jun.yang@nxp.com>
> Signed-off-by: Gagandeep Singh <g.singh@nxp.com>
There was a network issue when testing this series in GHA.
Recheck-request: github-robot
--
David Marchand
prev parent reply other threads:[~2024-10-10 7:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 8:43 [PATCH] " Gagandeep Singh
2024-10-07 8:48 ` David Marchand
2024-10-07 15:25 ` Stephen Hemminger
2024-10-09 5:07 ` [v2] " Gagandeep Singh
2024-10-09 21:01 ` [EXTERNAL] " Akhil Goyal
2024-10-10 5:52 ` Gagandeep Singh
2024-10-10 6:03 ` [v3] " Gagandeep Singh
2024-10-10 7:06 ` David Marchand [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='CAJFAV8yA1m5GyHQC=ucaqXrMRFUVe7KffeZAa-EeSkP44dL_gw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=g.singh@nxp.com \
--cc=hemant.agrawal@nxp.com \
--cc=jun.yang@nxp.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).