netdev - Re: [PATCH net-next 0/2] net/mlx4: Add dynamic policy changes to the SRIOV eSwitch support

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]

Date:	Tue, 2 Jul 2013 07:40:21 +0300
From:	Or Gerlitz <or.gerlitz@...il.com>
To:	David Miller <davem@...emloft.net>
Cc:	ogerlitz@...lanox.com, netdev@...r.kernel.org,
	jackm@....mellanox.co.il, ronye@...lanox.com
Subject: Re: [PATCH net-next 0/2] net/mlx4: Add dynamic policy changes to the
 SRIOV eSwitch support

On Mon, Jul 1, 2013 at 11:12 PM, David Miller <davem@...emloft.net> wrote:
>
> From: Or Gerlitz <ogerlitz@...lanox.com>
> Date: Thu, 27 Jun 2013 19:05:20 +0300
>
> > This patch set from Jack and Rony uses the UPDATE_QP new firmware
> > command
> > to allow for dynamic policy changes of PF controlled VF vlan/qos and
> > link-state.
> >
> > Done against net-next commit 8599b52e14 "bonding: add an option to fail
> > when any
> > of arp_ip_target is inaccessible"
>
> Applied, but in patch #2:
>
> +               /* even if the UPDATE_QP command isn't supported, we still want
> +                * to set this VF link according to the admin directive
> +                */
>
> Those last two lines start with a space, then TAB(s), which I had to
> fix up.  GIT even warns about this when I apply your patches.

thanks, last time similar thing happened I said that next time I will
double check, so I probably need to move into triple checking... I
will do little investigation later today to see how come there were no
complaints on my system.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html