DPDK patches and discussions
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
	 dev@dpdk.org, stable@dpdk.org,
	 David Marchand <david.marchand@redhat.com>,
	 Bruce Richardson <bruce.richardson@intel.com>,
	Patrick Robb <probb@iol.unh.edu>
Subject: Re: [PATCH V2] examples/pipeline: fix include path for rte_log.h
Date: Wed, 14 Feb 2024 11:25:31 -0500	[thread overview]
Message-ID: <f7t34tvhv2c.fsf@redhat.com> (raw)
In-Reply-To: <ffc2e35d-58ba-4768-bb52-e1175a8d605f@amd.com> (Ferruh Yigit's message of "Wed, 14 Feb 2024 11:22:16 +0000")

Ferruh Yigit <ferruh.yigit@amd.com> writes:

> 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
>> 
>
> Hi Cristian,
>
> How can I verify the fix? Can you please list the required steps?

I guess maybe (?) with the pipeline DTS case, but I'm not sure that
would be sufficient.

> And I wonder how this skipped the testing, I guess v23.11 released with
> this defect. Is there a gap in the CI or internal build/test scripts?

I don't know that softnic driver is used in the lab.  Actually, would
DTS suite even have triggered this issue?  I'm not sure if there is a
set of tests which covers the case.  Maybe Patrick can confirm about the
pipeline test?

>> Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
>> ---
>>  drivers/net/softnic/rte_eth_softnic_cli.c | 2 ++
>>  examples/pipeline/cli.c                   | 2 ++
>>  2 files changed, 4 insertions(+)
>> 
>> diff --git a/drivers/net/softnic/rte_eth_softnic_cli.c b/drivers/net/softnic/rte_eth_softnic_cli.c
>> index 085523fe03..95e705c553 100644
>> --- a/drivers/net/softnic/rte_eth_softnic_cli.c
>> +++ b/drivers/net/softnic/rte_eth_softnic_cli.c
>> @@ -337,6 +337,7 @@ cmd_softnic_pipeline_libbuild(struct pmd_internals *softnic __rte_unused,
>>  		 "-I %s/lib/eal/include "
>>  		 "-I %s/lib/eal/x86/include "
>>  		 "-I %s/lib/eal/include/generic "
>> +		 "-I %s/lib/log "
>>  		 "-I %s/lib/meter "
>>  		 "-I %s/lib/port "
>>  		 "-I %s/lib/table "
>> @@ -361,6 +362,7 @@ cmd_softnic_pipeline_libbuild(struct pmd_internals *softnic __rte_unused,
>>  		 install_dir,
>>  		 install_dir,
>>  		 install_dir,
>> +		 install_dir,
>>  		 log_file,
>>  		 obj_file,
>>  		 lib_file,
>> diff --git a/examples/pipeline/cli.c b/examples/pipeline/cli.c
>> index 2ae6cc579f..afb143c01f 100644
>> --- a/examples/pipeline/cli.c
>> +++ b/examples/pipeline/cli.c
>> @@ -714,6 +714,7 @@ cmd_pipeline_libbuild(char **tokens,
>>  		 "-I %s/lib/eal/include "
>>  		 "-I %s/lib/eal/x86/include "
>>  		 "-I %s/lib/eal/include/generic "
>> +		 "-I %s/lib/log "
>>  		 "-I %s/lib/meter "
>>  		 "-I %s/lib/port "
>>  		 "-I %s/lib/table "
>> @@ -738,6 +739,7 @@ cmd_pipeline_libbuild(char **tokens,
>>  		 install_dir,
>>  		 install_dir,
>>  		 install_dir,
>> +		 install_dir,
>>  		 log_file,
>>  		 obj_file,
>>  		 lib_file,


  reply	other threads:[~2024-02-14 16:25 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 [this message]
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

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=f7t34tvhv2c.fsf@redhat.com \
    --to=aconole@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=probb@iol.unh.edu \
    --cc=stable@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).