[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <82a6780a-71d5-746a-aa69-c2bc32755979@linaro.org>
Date: Fri, 24 Feb 2023 10:36:54 +0000
From: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To: Elliot Berman <quic_eberman@...cinc.com>,
Alex Elder <elder@...aro.org>,
Prakruthi Deepak Heragu <quic_pheragu@...cinc.com>
Cc: Murali Nalajala <quic_mnalajal@...cinc.com>,
Trilok Soni <quic_tsoni@...cinc.com>,
Srivatsa Vaddagiri <quic_svaddagi@...cinc.com>,
Carl van Schaik <quic_cvanscha@...cinc.com>,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Jonathan Corbet <corbet@....net>,
Bagas Sanjaya <bagasdotme@...il.com>,
Catalin Marinas <catalin.marinas@....com>,
Jassi Brar <jassisinghbrar@...il.com>,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v10 12/26] gunyah: vm_mgr: Add/remove user memory regions
On 24/02/2023 00:43, Elliot Berman wrote:
>>> +/*
>>> + * ioctls for VM fds
>>> + */
>>> +
>>> +/**
>>> + * struct gh_userspace_memory_region - Userspace memory descripion
>>> for GH_VM_SET_USER_MEM_REGION
>>> + * @label: Unique identifer to the region.
>>> + * @flags: Flags for memory parcel behavior
>>> + * @guest_phys_addr: Location of the memory region in guest's memory
>>> space (page-aligned)#
>>
>> Note about overlapping here would be useful.
>>
>
> I'd like to reduce duplicate documentation where possible. I was
This is exactly what .rst files can provide.
If you have a proper kernel-doc type documentation in header/source
files, these can be directly used in .rst files.
The reStructuredText (.rst) files may contain directives to include
structured documentation comments, or kernel-doc comments, from source
files.
ex:
.. kernel-doc:: include/linux/gunyah.h
:internal:
--srini
> generally following this procedure:
> - include/uapi/linux/gunyah.h docstrings have basic information to
> remind what the field is
> - Documentation/virt/gunyah/ documentation explains how to properly
> use the APIs
>
> I think it's definitely good idea to have separate documentation beyond
> what can be described in docstrings here.
>
> Thanks,
> Elliot
Powered by blists - more mailing lists