From: Thomas Monjalon <thomas@monjalon.net>
To: Emma Kenny <emma.kenny@intel.com>
Cc: dev@dpdk.org, Shahaf Shuler <shahafs@mellanox.com>,
"anatoly.burakov@intel.com" <anatoly.burakov@intel.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1] examples/multi_process: fix build error
Date: Wed, 11 Jul 2018 19:24:28 +0200 [thread overview]
Message-ID: <2027379.4iOr1NQnDj@xps> (raw)
In-Reply-To: <DB7PR05MB44266BBCE9EC17D66E0C15D7C3420@DB7PR05MB4426.eurprd05.prod.outlook.com>
03/07/2018 14:10, Shahaf Shuler:
> Monday, July 2, 2018 6:40 PM, Emma Kenny:
> > Subject: [PATCH v1] examples/multi_process: fix build error
> >
> > 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>
>
> Acked-by: Shahaf Shuler <shahafs@mellanox.com>
Applied, thanks
prev parent reply other threads:[~2018-07-11 17:24 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
2018-07-03 12:10 ` Shahaf Shuler
2018-07-11 17:24 ` Thomas Monjalon [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=2027379.4iOr1NQnDj@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=emma.kenny@intel.com \
--cc=ferruh.yigit@intel.com \
--cc=shahafs@mellanox.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).