: [PATCH] docs: specify stability of hypfs path documentation
In docs/misc/hypfs-paths.pandoc the supported paths in the hypervisor
file system are specified. Make it more clear that path availability
might change, e.g. due to scope widening or narrowing (e.g. being
limited to a specific
On 13.07.20 10:07, Jan Beulich wrote:
On 13.07.2020 10:04, Jürgen Groß wrote:
On 13.07.20 09:56, Jan Beulich wrote:
On 13.07.2020 07:16, Juergen Gross wrote:
@@ -55,6 +58,11 @@ tags enclosed in square brackets.
* CONFIG_* -- Path is valid only in case the hypervisor was built with
the
> Liu
> Subject: [PATCH] docs: specify stability of hypfs path documentation
>
> In docs/misc/hypfs-paths.pandoc the supported paths in the hypervisor
> file system are specified. Make it more clear that path availability
> might change, e.g. due to scope widening or narrowing
On 13.07.2020 10:04, Jürgen Groß wrote:
> On 13.07.20 09:56, Jan Beulich wrote:
>> On 13.07.2020 07:16, Juergen Gross wrote:
>>> @@ -55,6 +58,11 @@ tags enclosed in square brackets.
>>> * CONFIG_* -- Path is valid only in case the hypervisor was built with
>>> the respective config option.
>>
On 13.07.20 09:56, Jan Beulich wrote:
On 13.07.2020 07:16, Juergen Gross wrote:
@@ -55,6 +58,11 @@ tags enclosed in square brackets.
* CONFIG_* -- Path is valid only in case the hypervisor was built with
the respective config option.
+Path availability is subject to change, e.g. a speci
On 13.07.2020 07:16, Juergen Gross wrote:
> @@ -55,6 +58,11 @@ tags enclosed in square brackets.
> * CONFIG_* -- Path is valid only in case the hypervisor was built with
>the respective config option.
>
> +Path availability is subject to change, e.g. a specific path specified
> +for a single
In docs/misc/hypfs-paths.pandoc the supported paths in the hypervisor
file system are specified. Make it more clear that path availability
might change, e.g. due to scope widening or narrowing (e.g. being
limited to a specific architecture).
Signed-off-by: Juergen Gross
---
This might be a candid
