DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Emma Kenny <emma.kenny@intel.com>, dev@dpdk.org
Cc: anatoly.burakov@intel.com, shahafs@mellanox.com,
	dpdk-stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1] examples/multi_process: fix build error
Date: Mon, 2 Jul 2018 16:55:19 +0100	[thread overview]
Message-ID: <41d240ef-1afb-955c-9d4c-08cc9dae5f1f@intel.com> (raw)
In-Reply-To: <20180702154021.17908-1-emma.kenny@intel.com>

On 7/2/2018 4:40 PM, Emma Kenny wrote:
> Fix bug with undeclared variable name and
> calling a variable that is not member of struct.
> 
> CC main.o
> l2fwd_fork/main.c:  In function ‘main’: l2fwd_fork/main.c:1043:33:
>  error: ‘dev_info’ undeclared (first use in this function)
>  rte_eth_dev_info_get(portid, &dev_info);
> 
> l2fwd_fork/main.c:1043:33: note: each undeclared identifier is
> reported only once for each function it appears in
> l2fwd_fork/main.c:1077:11: error: ‘struct rte_eth_txconf’
> has no member named ‘tx_offloads’
>    txq_conf.tx_offloads = local_port_conf.txmode.offloads;
> 
> make[1]: *** [main.o] Error 1
> make: *** [all] Error 2
> 
> Fixes: f8c02ca878af ("examples/multi_process: convert to new ethdev offloads API")
> Cc: shahafs@mellanox.com
> 
> Signed-off-by: Emma Kenny <emma.kenny@intel.com>

Cc: stable@dpdk.org

Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>

  reply	other threads:[~2018-07-02 15:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-02 15:40 Emma Kenny
2018-07-02 15:55 ` Ferruh Yigit [this message]
2018-07-03 12:10 ` Shahaf Shuler
2018-07-11 17:24   ` Thomas Monjalon

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=41d240ef-1afb-955c-9d4c-08cc9dae5f1f@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=emma.kenny@intel.com \
    --cc=shahafs@mellanox.com \
    --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).