netdev - Re: Pull request: sfc-next 2012-12-01

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: <20121201.113323.892001865049602196.davem@davemloft.net>
Date:	Sat, 01 Dec 2012 11:33:23 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	bhutchings@...arflare.com
Cc:	netdev@...r.kernel.org, linux-net-drivers@...arflare.com
Subject: Re: Pull request: sfc-next 2012-12-01

From: Ben Hutchings <bhutchings@...arflare.com>
Date: Sat, 1 Dec 2012 04:40:21 +0000

> The following changes since commit bb728820fe7c42fdb838ab2745fb5fe6b18b5ffa:
> 
>   core: make GRO methods static. (2012-11-29 13:18:32 -0500)
> 
> are available in the git repository at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/bwh/sfc-next.git for-davem
> 
> (commit b9cc977d9d4d1866ee83df38815f4b3b34d99dd9)
> 
> 1. More workarounds for TX queue flush failures that can occur during
>    interface reconfiguration.
> 2. Fix spurious failure of a firmware request running during a system
>    clock change, e.g. ntpd started at the same time as driver load.
> 3. Fix inconsistent statistics after a firmware upgrade.
> 4. Fix a variable (non-)initialisation in offline self-test that can
>    make it more disruptive than intended.
> 5. Fix a race that can (at least) cause an assertion failure.
> 6. Miscellaneous cleanup.

Pulled, thanks a lot Ben.

I just want to point out how much I like your commit messages,
your patches are trivial to review because of them.

Thanks again.
--
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