Soft Patch Panel
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Cc: spp@dpdk.org, nakamura.hioryuki@po.ntt-tx.co.jp
Subject: Re: [spp] [PATCH] spp_vf: fix build
Date: Thu, 1 Feb 2018 12:01:30 +0000	[thread overview]
Message-ID: <150f2123-5520-1786-1830-5b2d68069bff@intel.com> (raw)
In-Reply-To: <fa24a961-04d2-2f32-1811-62d15e6555b8@lab.ntt.co.jp>

On 1/30/2018 3:55 AM, Yasufumi Ogawa wrote:
> On 2018/01/22 23:25, Ferruh Yigit wrote:
>> build error:
>> ...spp/src/vf/classifier_mac.c:314:5:
>>     error: format specifies type 'unsigned short' but the argument
>>            has type 'int' [-Werror,-Wformat]
>> 	classified_data->num_pkt - n_tx, classified_data->port);
>> 	^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> ...build/include/rte_log.h:316:32:
>>     note: expanded from macro 'RTE_LOG'
>> 	 RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__)
>> 				     ^~~~~~~~~~~
>>
>> Looks like caused by integer promotion, to fix cast variable
>> explicityly to uint16_t.
> 
> Ferruh,
> 
> Thanks for your contribution. Although I compiled Hiroyuki's patch with 
> DPDK 17.11 release (tagged as v17.11) and there is no error, but error 
> is occured after replacing DPDK latest.
> 
> ...spp/src/vf/spp_vf.c:931:28: error: ‘RTE_LOG_LEVEL’ undeclared (first 
> use in this function)
>     rte_log_set_global_level(RTE_LOG_LEVEL);
> 
> ...spp/src/vf/spp_vf.c:931:28: note: each undeclared identifier is 
> reported only once for each function it appears in
> /home/dpdk1711/dpdk-home/dpdk/mk/internal/rte.compile-pre.mk:114: ...
> 
> It is different from your error, but caused by rte_log. I think it is 
> possibly because of a change of rte_log after 17.11 release. In any 
> case, I think your change should be merged.
> 
> Acked-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>

Applied, thanks.

      reply	other threads:[~2018-02-01 12:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-22 14:25 Ferruh Yigit
2018-01-30  3:55 ` Yasufumi Ogawa
2018-02-01 12:01   ` 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=150f2123-5520-1786-1830-5b2d68069bff@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=nakamura.hioryuki@po.ntt-tx.co.jp \
    --cc=ogawa.yasufumi@lab.ntt.co.jp \
    --cc=spp@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).