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]
Message-ID: <425b30ac-623c-065e-1a2f-fc131dee28d1@web.de>
Date:   Sun, 14 Jul 2019 19:12:24 +0200
From:   Markus Elfring <Markus.Elfring@....de>
To:     Keyur Patel <iamkeyur96@...il.com>, devel@...verdev.osuosl.org,
        kernel-janitors@...r.kernel.org
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Christian Gromm <christian.gromm@...rochip.com>,
        Eugeniu Rosca <erosca@...adit-jv.com>,
        Suresh Udipi <sudipi@...adit-jv.com>,
        Colin Ian King <colin.king@...onical.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [v4] staging: most: Delete an error message for a failed memory
 allocation

> I think commit message is clear enough to understand why this is needed.

There are differences to consider between the involved software developers.


> You can send me what should I include in commit description

The clarification should be continued with the number “v5”
in the message subject.


> and I will add and send it again. Otherwise, Greg can comment on this.

Would you like to recheck information sources for the safe description
of the Linux allocation failure report?

Regards,
Markus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ