netdev - Re: [PATCH net-next 0/2] sfc: TX PIO fixes

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: <20170116.140136.2122671601212176674.davem@davemloft.net>
Date:   Mon, 16 Jan 2017 14:01:36 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     ecree@...arflare.com
Cc:     linux-net-drivers@...arflare.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next 0/2] sfc: TX PIO fixes

From: Edward Cree <ecree@...arflare.com>
Date: Fri, 13 Jan 2017 21:18:38 +0000

> Edward Cree (2):
>   sfc: allow PIO more often
>   sfc: get PIO buffer size from the NIC

Both patches applied, thanks.

When you give me a completely content free header posting like this, it
is basically worthless to me and I don't even use it.

Please put some real content into this header posting, explaining what
the series is doing at a high level, how it is doing it, and why it is
doing it that way.

Thanks.