linux-kernel - Re: [PATCH 0/1] Use memset

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] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 18 Sep 2020 11:05:57 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Shane Chien <shane.chien@...iatek.com>
Cc:     Matthias Brugger <matthias.bgg@...il.com>,
        linux-kernel@...r.kernel.org, linux-mediatek@...ts.infradead.org,
        devicetree@...r.kernel.org, wsd_upstream@...iatek.com,
        jiaxin.yu@...iatek.com, eason.yen@...iatek.com
Subject: Re: [PATCH 0/1] Use memset_io to access I/O memory

On Fri, Sep 18, 2020 at 06:00:18PM +0800, Shane Chien wrote:
> From: "Shane.Chien" <shane.chien@...iatek.com>
> 
> Use memset_io to access I/O memory, instead of
> memset.

Please don't send cover letters for single patches, if there is anything
that needs saying put it in the changelog of the patch or after the ---
if it's administrative stuff.  This reduces mail volume and ensures that 
any important information is recorded in the changelog rather than being
lost. 

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)