From: David Marchand <david.marchand@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
Akhil Goyal <gakhil@marvell.com>
Cc: dev@dpdk.org, Fan Zhang <fanzhang.oss@gmail.com>
Subject: Re: [PATCH] cryptodev: convert to dynamic logtype
Date: Tue, 12 Dec 2023 08:50:34 +0100 [thread overview]
Message-ID: <CAJFAV8z+A4jtDjNnfxFmj2VgUt5Z2R_Ftfrs2tdwZB38ZecFMA@mail.gmail.com> (raw)
In-Reply-To: <20231211201733.127771-1-stephen@networkplumber.org>
On Mon, Dec 11, 2023 at 9:18 PM Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> The cryptodev logs are all referenced via rte_crytpodev.h
crypto*
> so make it dynamic there.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
I would add a comment in the header that this exported logtype
variable is for internal use.
Otherwise it lgtm.
Akhil, do you mind if I take this directly in main?
--
David Marchand
next prev parent reply other threads:[~2023-12-12 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 20:17 Stephen Hemminger
2023-12-12 7:50 ` David Marchand [this message]
2023-12-12 8:14 ` [EXT] " Akhil Goyal
2023-12-12 13:01 ` David Marchand
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=CAJFAV8z+A4jtDjNnfxFmj2VgUt5Z2R_Ftfrs2tdwZB38ZecFMA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=gakhil@marvell.com \
--cc=stephen@networkplumber.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).