From: Stephen Hemminger <stephen@networkplumber.org>
To: bugzilla@dpdk.org
Cc: dev@dpdk.org
Subject: Re: [Bug 1335] [dpdk-24.03-rc0] freebsd/nic_uio meson build error with clang16.0.6 and gcc12.2.0 on FreeBSD14
Date: Tue, 19 Dec 2023 09:14:45 -0800 [thread overview]
Message-ID: <20231219091445.70939a4f@hermes.local> (raw)
In-Reply-To: <bug-1335-3@http.bugs.dpdk.org/>
On Tue, 19 Dec 2023 07:46:18 +0000
bugzilla@dpdk.org wrote:
> # git log -1
> commit e5dc404d33ac1c6cea5c62a88489746c5cb5e35e (HEAD, origin/main,
> origin/HEAD, main)
> Author: Stephen Hemminger <stephen@networkplumber.org>
> Date: Mon Dec 11 12:17:32 2023 -0800
>
> cryptodev: use a dynamic logtype
>
> The cryptodev logs are all referenced via rte_cryptodev.h,
> so make it dynamic there.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> Acked-by: Akhil Goyal <gakhil@marvell.com>
This patch did not touch the FreeBSD driver, it is a pre-existing condition.
next prev parent reply other threads:[~2023-12-19 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 7:46 bugzilla
2023-12-19 17:14 ` Stephen Hemminger [this message]
2024-02-20 23:34 ` [DPDK/core Bug " bugzilla
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=20231219091445.70939a4f@hermes.local \
--to=stephen@networkplumber.org \
--cc=bugzilla@dpdk.org \
--cc=dev@dpdk.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).