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, 20 Jul 2022 06:27:14 -0600
From:   Jonathan Corbet <corbet@....net>
To:     "Jason A. Donenfeld" <Jason@...c4.com>, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org
Cc:     "Jason A. Donenfeld" <Jason@...c4.com>,
        Simon Sapin <simon.sapin@...r.org>,
        Gabriel Somlo <somlo@....edu>
Subject: Re: [PATCH] docs: ABI: correct QEMU fw_cfg spec path

"Jason A. Donenfeld" <Jason@...c4.com> writes:

> A few weeks ago, QEMU switched docs/specs/fw_cfg.txt to be
> docs/specs/fw_cfg.rst, so update the reference in the kernel docs to
> reflect this.
>
> Cc: Simon Sapin <simon.sapin@...r.org>
> Cc: Gabriel Somlo <somlo@....edu>
> Cc: Jonathan Corbet <corbet@....net>
> Signed-off-by: Jason A. Donenfeld <Jason@...c4.com>
> ---
>  Documentation/ABI/testing/sysfs-firmware-qemu_fw_cfg | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-firmware-qemu_fw_cfg b/Documentation/ABI/testing/sysfs-firmware-qemu_fw_cfg
> index ee0d6dbc810e..7cbce4af6346 100644
> --- a/Documentation/ABI/testing/sysfs-firmware-qemu_fw_cfg
> +++ b/Documentation/ABI/testing/sysfs-firmware-qemu_fw_cfg
> @@ -12,7 +12,7 @@ Description:
>  		configuration data to the guest userspace.
>  
>  		The authoritative guest-side hardware interface documentation
> -		to the fw_cfg device can be found in "docs/specs/fw_cfg.txt"
> +		to the fw_cfg device can be found in "docs/specs/fw_cfg.rst"
>  		in the QEMU source tree.

This is a worthy change, but is there any chance we could provide a URL
instead so that people don't have to go finding the QEMU source to get
the information they need?

Thanks,

jon

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ