netdev - Re: [PATCH net-next V2 00/16] Mellanox 100G SRIOV E-Switch offload and VF representors

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CALzJLG_98jBdK62B=bN4=C8xdEL4zp2=mZOMOfJGv_n+JXNNGA@mail.gmail.com>
Date:	Fri, 1 Jul 2016 14:04:04 +0300
From:	Saeed Mahameed <saeedm@....mellanox.co.il>
To:	David Miller <davem@...emloft.net>
Cc:	Saeed Mahameed <saeedm@...lanox.com>,
	Linux Netdev List <netdev@...r.kernel.org>,
	Or Gerlitz <ogerlitz@...lanox.com>,
	Hadar Har-Zion <hadarh@...lanox.com>,
	Jiri Pirko <jiri@...lanox.com>, gospo@...ulusnetworks.com,
	jesse.brandeburg@...el.com,
	John Fastabend <john.r.fastabend@...el.com>
Subject: Re: [PATCH net-next V2 00/16] Mellanox 100G SRIOV E-Switch offload
 and VF representors

On Fri, Jul 1, 2016 at 1:16 PM, David Miller <davem@...emloft.net> wrote:
>
> So you have submitted to me, in parallel, two non-trivial sets of changes
> to the mlx5 driver.  One for 'net' and one for 'net-next, and at the same
> exact time.
>
> You haven't given me any indication of whether there are any dependencies
> nor conflicts from these two sets of changes.
>

Right,

Now that i see you've merged 'f5074d0ce2f8 Merge branch
'mlx5-100G-fixes'' ino net-next

the last patch "net/mlx5e: Introduce SRIOV VF representors" will
encounter the following compilation error

drivers/net/ethernet/mellanox/mlx5/core/en_rep.c: In function
'mlx5e_rep_get_strings':
drivers/net/ethernet/mellanox/mlx5/core/en_rep.c:68:31: error: 'const
struct counter_desc' has no member named 'name'
           sw_rep_stats_desc[i].name);

I will rebase, fix and respin.

Regarding the latest fixes you applied today ''resiliency and xmit
path fixes", there will be two trivial conflicts (not related to this
series) once net is merged into net-next.

I will send you details on that mail thread.