From: "Patil, Harish" <Harish.Patil@cavium.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
"Mody, Rasesh" <Rasesh.Mody@cavium.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>, DPDK <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v7 1/7] qede: add base driver
Date: Wed, 19 Apr 2017 15:44:05 +0000 [thread overview]
Message-ID: <D51CD38C.133582%Harish.Patil@cavium.com> (raw)
In-Reply-To: <0d9df1f9-688f-e7ab-15c2-4288c700aaa8@intel.com>
>
><...>
>
>>>> +
>>>> +#
>>>> +# Add extra flags for base ecore driver files # to disable warnings
>>>> +in them # # BASE_DRIVER_OBJS=$(patsubst %.c,%.o,$(notdir $(wildcard
>>>> +$(SRCDIR)/base/*.c))) $(foreach obj, $(BASE_DRIVER_OBJS), $(eval
>>>> +CFLAGS+=$(CFLAGS_BASE_DRIVER)))
>>>
>>> My eyes just caught this one, above line adds $(CFLAGS_BASE_DRIVER)
>>> many times to $(CFLAGS), but real intentions is add to obj specific
>>>CFLAGS
>>> and only being limited to base files.
>>>
>>> Like:
>>> $(foreach obj, $(BASE_DRIVER_OBJS), $(eval
>>> CFLAGS_$(obj)+=$(CFLAGS_BASE_DRIVER)))
>>>
>>> Can you please fix this?
>>
>> We will look into this, we plan to submit the fix as separate bug fix
>>patch in 17.05 timeframe.
>
>Reminder.
Hi Ferruh,
Yes, we are going to submit this along side few bug fixes.
Thanks.
>
>>
>> Thanks!
>> -Rasesh
>>
>>>
>>> Fixing this may give some build errors on non-base driver files,
>>>although not
>>> sure.
>>>
>>> Thanks,
>>> ferruh
>
next prev parent reply other threads:[~2017-04-19 15:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 14:18 [dpdk-dev] [PATCH v7 0/7] qede: add qede PMD Rasesh Mody
2016-04-27 14:18 ` [dpdk-dev] [PATCH v7 1/7] qede: add base driver Rasesh Mody
2017-03-28 11:16 ` Ferruh Yigit
2017-03-28 21:04 ` Mody, Rasesh
2017-04-19 15:19 ` Ferruh Yigit
2017-04-19 15:44 ` Patil, Harish [this message]
2016-04-27 14:18 ` [dpdk-dev] [PATCH v7 2/7] qede: add core driver Rasesh Mody
2016-04-27 14:18 ` [dpdk-dev] [PATCH v7 3/7] qede: enable PMD build Rasesh Mody
2016-04-27 14:18 ` [dpdk-dev] [PATCH v7 4/7] qede: add L2 support Rasesh Mody
2016-04-27 14:18 ` [dpdk-dev] [PATCH v7 5/7] qede: add SRIOV support Rasesh Mody
2016-04-27 14:18 ` [dpdk-dev] [PATCH v7 6/7] qede: add interrupt handling support Rasesh Mody
2016-04-27 14:18 ` [dpdk-dev] [PATCH v7 7/7] qede: add DCBX support Rasesh Mody
2016-04-27 16:05 ` [dpdk-dev] [PATCH v7 0/7] qede: add qede PMD Bruce Richardson
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=D51CD38C.133582%Harish.Patil@cavium.com \
--to=harish.patil@cavium.com \
--cc=Rasesh.Mody@cavium.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=thomas.monjalon@6wind.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).