linux-kernel - Re: [PATCH] regulator: fix memory leak on error path of regulator

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

Message-ID: <1e281322-c589-9c36-0565-98fccf5f0e17@web.de>
Date:   Fri, 24 Jul 2020 09:09:35 +0200
From:   Markus Elfring <Markus.Elfring@....de>
To:     Vladimir Zapolskiy <vz@...ia.com>, kernel-janitors@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org, Liam Girdwood <lgirdwood@...il.com>,
        Mark Brown <broonie@...nel.org>,
        Wen Yang <wenyang@...ux.alibaba.com>
Subject: Re: [PATCH] regulator: fix memory leak on error path of
 regulator_register()

> … introduced as a side ef another …

Would the following wording variant be more appropriate?

  … introduced as a side effect of another …


How do you think about to replace the wording “…, I believe …”
by an imperative description?

Regards,
Markus