linux-kernel - Re: [PATCH 00/14] drop double zeroing

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:   Wed, 23 Sep 2020 17:10:33 +0200
From:   Rolf Reintjes <lists2.rolf@...ntjes.nrw>
To:     Mark Brown <broonie@...nel.org>, linux-spi@...r.kernel.org,
        Julia Lawall <Julia.Lawall@...ia.fr>
Cc:     linux-serial@...r.kernel.org, linux-scsi@...r.kernel.org,
        target-devel@...r.kernel.org, kernel-janitors@...r.kernel.org,
        linux-media@...r.kernel.org, linux-block@...r.kernel.org,
        Yossi Leybovich <sleybo@...zon.com>,
        linux-kernel@...r.kernel.org, linux-nfs@...r.kernel.org,
        dmaengine@...r.kernel.org, linux-pci@...r.kernel.org,
        netdev@...r.kernel.org, linux-wireless@...r.kernel.org,
        linux-rdma@...r.kernel.org,
        Dan Williams <dan.j.williams@...el.com>,
        rds-devel@....oracle.com
Subject: Re: [PATCH 00/14] drop double zeroing

Hello Mark,

On 21.09.20 18:58, Mark Brown wrote:
> On Sun, 20 Sep 2020 13:26:12 +0200, Julia Lawall wrote:
>> sg_init_table zeroes its first argument, so the allocation of that argument
>> doesn't have to.
> 
> Applied to
> 
>     https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
> 
> Thanks!

I do not understand which of the 14 patches you applied. Your mail 
responds to the 00/14 mail.

Rolf

> 
> [1/1] spi/topcliff-pch: drop double zeroing
>        commit: ca03dba30f2b8ff45a2972c6691e4c96d8c52b3b
> 
> All being well this means that it will be integrated into the linux-next
> tree (usually sometime in the next 24 hours) and sent to Linus during
> the next merge window (or sooner if it is a bug fix), however if
> problems are discovered then the patch may be dropped or reverted.
> 
> You may get further e-mails resulting from automated or manual testing
> and review of the tree, please engage with people reporting problems and
> send followup patches addressing any issues that are reported if needed.
> 
> If any updates are required or you are submitting further changes they
> should be sent as incremental updates against current git, existing
> patches will not be replaced.
> 
> Please add any relevant lists and maintainers to the CCs when replying
> to this mail.
> 
> Thanks,
> Mark
>