From: Xueming Li <xuemingl@nvidia.com>
To: David Marchand <david.marchand@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Yu Jiang <yux.jiang@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH v2] eal/unix: support ZSTD compression for firmware
Date: Wed, 3 Jul 2024 09:03:09 +0000 [thread overview]
Message-ID: <DM4PR12MB5373ACBDB6A60BC6A52472CEA1DD2@DM4PR12MB5373.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8wGw3WV3V-q4fFuxo1en4Z8M96iojMmaSd1M7e6+54GWg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
Thanks, I tried but missed the "EAL" part :-)
________________________________
From: David Marchand <david.marchand@redhat.com>
Sent: Wednesday, July 3, 2024 3:27 PM
To: Xueming Li <xuemingl@nvidia.com>
Cc: dev@dpdk.org <dev@dpdk.org>; Yu Jiang <yux.jiang@intel.com>; Bruce Richardson <bruce.richardson@intel.com>; stable@dpdk.org <stable@dpdk.org>
Subject: Re: [PATCH v2] eal/unix: support ZSTD compression for firmware
On Wed, Jul 3, 2024 at 9:12 AM Xueming Li <xuemingl@nvidia.com> wrote:
>
> Hi David,
>
> I get unix compilation failure when backporting this patch to 23.11 LTS, the EAL_LOG macro is not backported to 23.11 LTS, any suggestion?
Like other logging calls in this same file, you can replace
EAL_LOG(level, fmt, args); with a simple RTE_LOG(level, EAL, fmt "\n",
args);
Am I missing something?
--------
--
David Marchand
[-- Attachment #2: Type: text/html, Size: 2158 bytes --]
prev parent reply other threads:[~2024-07-03 9:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240508095214.2541115-1-david.marchand@redhat.com>
2024-05-13 11:12 ` David Marchand
2024-05-13 11:37 ` Bruce Richardson
2024-05-13 11:47 ` David Marchand
2024-05-17 17:01 ` David Marchand
2024-07-03 7:12 ` Xueming Li
2024-07-03 7:27 ` David Marchand
2024-07-03 9:03 ` Xueming Li [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=DM4PR12MB5373ACBDB6A60BC6A52472CEA1DD2@DM4PR12MB5373.namprd12.prod.outlook.com \
--to=xuemingl@nvidia.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=yux.jiang@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).