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]
Date: Mon, 19 Feb 2024 14:36:55 -0700
From: Jonathan Corbet <corbet@....net>
To: Lukas Bulwahn <lukas.bulwahn@...il.com>, "Ran.Park" <ranpark@...mail.com>
Cc: ricardo@...liere.net, akinobu.mita@...il.com, linux-doc@...r.kernel.org,
 linux-kernel-mentees@...ts.linuxfoundation.org,
 linux-kernel@...r.kernel.org, skhan@...uxfoundation.org
Subject: Re: [PATCH] Fixed case issue with 'fault-injection' in documentation

Lukas Bulwahn <lukas.bulwahn@...il.com> writes:

> Ricardo suggests that:
>
> - you run 'make htmldocs' before applying the patch and check for the
> existing warnings.
>
> - you run 'make cleandocs' and 'make htmldocs' after applying the
> patch and check for the existing warnings.
>
> Did any warning disappear or appear due to your patch? Were you
> motivated by a specific warning you observed during the build and you
> addressing that?
>
> So, for starters: did you already try 'make htmldocs' with your patch
> applied? What did you observe?

This all seems like a bit much for what is essentially a typo fix.  I
would be amazed if it changed the build in any way other than making the
case more consistent; there's no need to do all that stuff.

I've applied it, thanks.

jon

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ