From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Cc: stable@dpdk.org, dev@dpdk.org,
Thomas Monjalon <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>
Subject: Re: [PATCH V2] examples/pipeline: fix include path for rte_log.h
Date: Thu, 15 Feb 2024 13:32:15 +0000 [thread overview]
Message-ID: <091536f2-88b7-4e77-bdfc-a3ec864f5df3@amd.com> (raw)
In-Reply-To: <20240213173809.1536955-1-cristian.dumitrescu@intel.com>
On 2/13/2024 5:38 PM, Cristian Dumitrescu wrote:
> When rte_log.h was moved to a new directory, the include path was not
> updated for the generated C code produced by the pipeline library,
> which results in build failure for this code.
>
> Fixes: 09ce41310930 ("log: separate logging functions out of EAL")
> Cc: stable@dpdk.org
>
> Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
>
Tested-by: Ferruh Yigit <ferruh.yigit@amd.com>
Patch has both net/softnic and examples/pipeline update, since update is
trivial and for exact same issue, instead of requesting a patch split I
am getting it directly to next-net to not create more overhead.
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2024-02-15 13:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 14:52 [PATCH] " Cristian Dumitrescu
2024-02-13 16:18 ` David Marchand
2024-02-13 17:22 ` Dumitrescu, Cristian
2024-02-13 17:38 ` [PATCH V2] " Cristian Dumitrescu
2024-02-14 11:22 ` Ferruh Yigit
2024-02-14 16:25 ` Aaron Conole
2024-02-14 19:32 ` Patrick Robb
2024-02-14 20:00 ` Dumitrescu, Cristian
2024-02-14 20:17 ` Patrick Robb
2024-02-14 17:22 ` Dumitrescu, Cristian
2024-02-15 12:17 ` Ferruh Yigit
2024-02-15 13:32 ` Ferruh Yigit [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=091536f2-88b7-4e77-bdfc-a3ec864f5df3@amd.com \
--to=ferruh.yigit@amd.com \
--cc=cristian.dumitrescu@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).