netdev - Re: [net-next 1/4] bna: Clear Driver Config Flags When HW Resets

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: <20130511.173848.1340042080692595063.davem@davemloft.net>
Date:	Sat, 11 May 2013 17:38:48 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	rmody@...cade.com
Cc:	netdev@...r.kernel.org, adapter_linux_open_src_team@...cade.com
Subject: Re: [net-next 1/4] bna: Clear Driver Config Flags When HW Resets

From: Rasesh Mody <rmody@...cade.com>
Date: Fri, 10 May 2013 10:02:14 -0700

>         Driver configuration flags are retained across open/stop operations
>         preventing configurations to be set in next open/stop.
>         Setting MTU on a 1020 causes network to fail until a reboot is performed
>         on the host.
> 
>         Clear the flags when configuration resets in hardware.

Please stop indenting your commit messages like this, nobody else
does this, so I cannot imagine where you observed this convention.

Resubmit this patch series with this corrected, thanks.
--
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