Re: [dpdk-dev] [PATCH] mk: disable new gcc truncation flag

2017-06-13 Thread Markos Chandras
On 06/13/2017 04:45 PM, Ferruh Yigit wrote: > On 6/13/2017 10:18 AM, Nirmoy Das wrote: >> >> >> On 06/12/2017 04:35 PM, Markos Chandras wrote: >>> On 06/02/2017 07:38 PM, Markos Chandras wrote: >>>> On 06/02/2017 05:31 PM, Nirmoy Das wrote: >>>

Re: [dpdk-dev] [PATCH] mk: disable new gcc truncation flag

2017-06-13 Thread Markos Chandras
On 06/13/2017 12:18 PM, Nirmoy Das wrote: > > > On 06/12/2017 04:35 PM, Markos Chandras wrote: >> On 06/02/2017 07:38 PM, Markos Chandras wrote: >>> On 06/02/2017 05:31 PM, Nirmoy Das wrote: >>>> disable truncation check to ignore below warning >>>&g

Re: [dpdk-dev] [PATCH] mk: disable new gcc truncation flag

2017-06-12 Thread Markos Chandras
On 06/02/2017 07:38 PM, Markos Chandras wrote: > On 06/02/2017 05:31 PM, Nirmoy Das wrote: >> disable truncation check to ignore below warning >> dpdk/x86_64-native-linuxapp-gcc-default/build/lib/librte_eal/linuxapp/kni/igb_main.c:2476:30: >> error: '%d' directive

Re: [dpdk-dev] [PATCH] mk: disable new gcc truncation flag

2017-06-02 Thread Markos Chandras
On 06/02/2017 05:31 PM, Nirmoy Das wrote: > disable truncation check to ignore below warning > dpdk/x86_64-native-linuxapp-gcc-default/build/lib/librte_eal/linuxapp/kni/igb_main.c:2476:30: > error: '%d' directive output may be truncated writing between 1 and 5 bytes > into a region of size betwee

Re: [dpdk-dev] [PATCH] pci: fix glibc 2.25 warning regarding major/minor definitions

2017-04-04 Thread Markos Chandras
Hi Nirmoy, On 04/04/2017 01:32 PM, Nirmoy Das wrote: > fixes: > error: In the GNU C Library, "makedev" is defined > by . For historical compatibility, it is > currently defined by as well, but we plan to > remove this soon. To use "makedev", include > directly. If you did not intend to use a sys

Re: [dpdk-dev] [PATCH] pci: fix glibc 2.25 warning regarding major/minor definitions

2017-04-04 Thread Markos Chandras
On 04/04/2017 01:50 PM, Markos Chandras wrote: > Hi Nirmoy, > > On 04/04/2017 01:32 PM, Nirmoy Das wrote: >> fixes: >> error: In the GNU C Library, "makedev" is defined >> by . For historical compatibility, it is >> currently defined by as well,

Re: [dpdk-dev] [PATCH] examples: ethtool: Link against librte_pmd_ixgbe if necessary

2017-02-17 Thread Markos Chandras
On 02/17/2017 04:11 PM, Remy Horton wrote: > > On 16/02/2017 16:17, Markos Chandras wrote: >> The librte_ethtool library depends on librte_pmd_ixgbe if that >> pmd driver is enabled so we need to link against it when we compile >> the ethtool application. It fixes the

[dpdk-dev] [PATCH] examples: ethtool: Link against librte_pmd_ixgbe if necessary

2017-02-16 Thread Markos Chandras
to `rte_pmd_ixgbe_set_vf_rxmode@DPDK_17.02' collect2: error: ld returned 1 exit status Cc: Nirmoy Das Signed-off-by: Markos Chandras --- examples/ethtool/ethtool-app/Makefile | 3 +++ 1 file changed, 3 insertions(+) diff --git a/examples/ethtool/ethtool-app/Makefile b/examples/ethtool/et

[dpdk-dev] [PATCH] e1000/base: Add missing braces to the 'if' statements

2016-06-27 Thread Markos Chandras
Hi Bruce, On 06/27/2016 03:39 PM, Bruce Richardson wrote: > On Thu, Jun 23, 2016 at 10:25:52AM +0100, Markos Chandras wrote: >> Add the missing braces to the 'if' statements to fix the misleading >> identation. This also fixes the following build errors when

[dpdk-dev] [PATCH] e1000/base: Add missing braces to the 'if' statements

2016-06-23 Thread Markos Chandras
gt; > -- > thanks > anupam > > > On Thu, Jun 23, 2016 at 2:55 PM, Markos Chandras > wrote: > >> Add the missing braces to the 'if' statements to fix the misleading >> identation. This also fixes the following build errors when building >> wit

[dpdk-dev] [PATCH] e1000/base: Add missing braces to the 'if' statements

2016-06-23 Thread Markos Chandras
.c:4221:2: error: this 'if' clause does not guard... [-Werror=misleading-indentation] if (locked) ^~ drivers/net/e1000/base/e1000_phy.c:4223:3: note: ...this statement, but the latter is misleadingly indented as if it is guarded by the 'if' if (!ready) ^~ Signed-off-by: Markos

[dpdk-dev] Suggestions for the dpdk stable tree

2016-05-20 Thread Markos Chandras
Hi, On 05/20/2016 04:54 PM, Christian Ehrhardt wrote: > Hi, > it would be great to have an actively maintained LTS release. > > Clearly all us "Distribution People" like Panu, Me and a few others should > - whenever bugs are identified as potential backports - start the > discussion. > And having

[dpdk-dev] [PATCH] mk: toolchain: gcc: query the compiler macros to obtain the gcc version

2016-03-23 Thread Markos Chandras
On 03/23/2016 09:49 AM, Thomas Monjalon wrote: > 2016-03-22 22:50, Markos Chandras: >> On 22/03/16 22:34, Thomas Monjalon wrote: >>> 2016-03-22 17:13, Markos Chandras: >>>> This is similar to what's being used in the Linux kernel. Querying the >>>>

[dpdk-dev] [PATCH] mk: toolchain: gcc: query the compiler macros to obtain the gcc version

2016-03-22 Thread Markos Chandras
Hi, On 22/03/16 22:34, Thomas Monjalon wrote: > 2016-03-22 17:13, Markos Chandras: >> This is similar to what's being used in the Linux kernel. Querying the >> GCC macros directly gives more accurate results compared to -dumpversion >> which could vary across distribu

[dpdk-dev] [PATCH] mk: toolchain: gcc: query the compiler macros to obtain the gcc version

2016-03-22 Thread Markos Chandras
This is similar to what's being used in the Linux kernel. Querying the GCC macros directly gives more accurate results compared to -dumpversion which could vary across distributions. Signed-off-by: Markos Chandras --- In openSUSE Tumbleweed (and in any other SUSE distribution which uses (or