netdev - Re: [PATCH 1/4] net: qrtr: Refactor packet allocation

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: <20170607.153546.1941397132398765014.davem@davemloft.net>
Date:   Wed, 07 Jun 2017 15:35:46 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     bjorn.andersson@...aro.org
Cc:     aneela@...eaurora.org, netdev@...r.kernel.org,
        linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
        ccavin@...il.com
Subject: Re: [PATCH 1/4] net: qrtr: Refactor packet allocation

A proper patch series must have a "[PATCH 0/N] ..." header posting
which explains what the patch series is doing at a high level, how
it is doing it, and why it is doing it that way.