From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: Sunil Uttarwar <sunilprakashrao.uttarwar@amd.com>
Subject: Re: [PATCH 6/6] crypto/ccp: use a dynamic logtype
Date: Fri, 28 Jun 2024 13:57:53 +0200 [thread overview]
Message-ID: <CAJFAV8xZjJcd-uP4dd1-UGMcVwoZJxo-t2pXVfu+pF93KWMagA@mail.gmail.com> (raw)
In-Reply-To: <20240625122414.1065829-7-david.marchand@redhat.com>
On Tue, Jun 25, 2024 at 2:25 PM David Marchand
<david.marchand@redhat.com> wrote:
> diff --git a/drivers/crypto/ccp/rte_ccp_pmd.c b/drivers/crypto/ccp/rte_ccp_pmd.c
> index 869399597e..022c1df182 100644
> --- a/drivers/crypto/ccp/rte_ccp_pmd.c
> +++ b/drivers/crypto/ccp/rte_ccp_pmd.c
> @@ -22,6 +22,7 @@
> static unsigned int ccp_pmd_init_done;
> uint8_t ccp_cryptodev_driver_id;
> uint8_t cryptodev_cnt;
> +int crypto_ccp_logtype;
This declaration is unneeded as RTE_LOG_REGISTER_DEFAULT declares the
logtype var.
I will fix in a new revision if one is needed, otherwise, I will fix
when applying.
>
> struct ccp_pmd_init_params {
> struct rte_cryptodev_pmd_init_params def_p;
--
David Marchand
prev parent reply other threads:[~2024-06-28 11:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 12:24 [PATCH 0/6] Some drivers logging cleanups David Marchand
2024-06-25 12:24 ` [PATCH 1/6] vdpa/sfc: remove dead code David Marchand
2024-06-25 14:25 ` Andrew Rybchenko
2024-06-25 12:24 ` [PATCH 2/6] drivers: use dedicated log macros instead of EAL logtype David Marchand
2024-06-25 12:24 ` [PATCH 3/6] net/sfc: remove use " David Marchand
2024-06-25 14:26 ` Andrew Rybchenko
2024-06-25 12:24 ` [PATCH 4/6] vdpa/sfc: " David Marchand
2024-06-25 12:24 ` [PATCH 5/6] bus/pci: use a dynamic logtype David Marchand
2024-06-26 2:05 ` Chenbo Xia
2024-06-25 12:24 ` [PATCH 6/6] crypto/ccp: " David Marchand
2024-06-28 11:57 ` 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=CAJFAV8xZjJcd-uP4dd1-UGMcVwoZJxo-t2pXVfu+pF93KWMagA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=sunilprakashrao.uttarwar@amd.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).