From: Stefan Herdler <herdler@nurfuerspam.de>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Hans Verkuil <hverkuil-cisco@xs4all.nl>,
linux-media@vger.kernel.org,
Manu Abraham <abraham.manu@gmail.com>,
Tomasz Maciej Nowak <tmn505@gmail.com>,
Corinna Vinschen <vinschen@redhat.com>,
Soeren Moch <smoch@web.de>
Subject: Re: [PATCH v2] Legacy DVB API: completion of documentation
Date: Mon, 3 Apr 2023 00:25:00 +0200 [thread overview]
Message-ID: <5b5a1dc0-96c4-c3c4-a24b-1917b39f8292@nurfuerspam.de> (raw)
In-Reply-To: <20230327192826.65ae299d@sal.lan>
Hi Mauro,
I just want to say thank you, for your very detailed review. It helps me a lot.
Now I know for sure which kind details have been missed.
Reading and writing such a documentation is definitely a different thing.
On 27/03/23 20:28, Mauro Carvalho Chehab wrote:
[...]
>
>>> At least everything in the header-files is in the documentation now. I hope, I have done it sufficiently.
>
> Good! It took me quite a while to read everything... At the end, as was
> a little tired, so I probably missed things.
>
> Next time, please split this on a patch series, in order to make
> easier for the poor reviewers to look into it ;-)
I have to apologies. I just realized, that it got that long,
while reading your answer.
I should have tried to scroll down to the end, before sending ;-).
[...]
>
>>> I haven't found any useful hint how to get rid of them.
>>> Should I switch to "code-block:: c" instead?
>>> But there are a lot of this warnings from other files too. It seems I'm mot the only one with this problem.
>> I switched to "code-block".
>> Now there are no warnings anymore.
>
> For things like ioctl, code-blocks are preferred. For other things,
> better to keep the warnings and not use code-block where not needed. The
> warnings are part of the Sphinx cross-reference system, which tries to
> create references to the C domain functions and data types.
>
> Unfortunately, Sphinx has a known bug that it is hit when the same symbol
> name is used with different meanings e.g., on C declarations like those:
>
> struct foo;
> enum foo;
> typedef foo;
> foo() {}
>
> Each one has a different type. So, `foo` cross-references depend on
> the context. Right now, Sphinx will just consider them to be attempts
> to re-define an existing name. There's already patches fixing it
> Sphinx upstream, but (last time I checked) not applied yet as those
> would cause regressions on intersphinx.
>
>> This functions shouldn't be referenced from outside this document anyway.
>
> No, we link the header files with the documentation, exactly to
> generate cross-references and detect gaps at the docsO.k., I thought this applies only to the inline-documentation generated from
source-code.
But it makes sense now.
Thanks to your tips I was able to find the solution for this problem in
minutes.
One of the versions I tried was already almost right. But I haven't seen it.
I already noticed, that not everything of the API is in use by the AV7110
driver, but I forgot it in the remarks.
I will provide a list next time.
I had searched for the declarations from the header-files in the projects
including them.
Almost everything was found in the AV7110 driver, only 2 or 3 items were
missing. And this rest seems to be used elsewhere.
My first target was to make the documentation consistent to the headers.
So I kept them, at least for now.
I'll mail again when I'm finished, but it may take a while.
Regards
Stefan
next prev parent reply other threads:[~2023-04-02 22:25 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 22:19 Future of the SAA7146 drivers Stefan Herdler
2023-01-31 8:45 ` Hans Verkuil
2023-01-31 23:56 ` Stefan Herdler
2023-02-01 9:15 ` Hans Verkuil
2023-02-01 11:35 ` Soeren Moch
2023-02-01 13:51 ` Hans Verkuil
2023-02-01 15:20 ` Soeren Moch
2023-02-01 16:37 ` Hans Verkuil
2023-02-08 8:42 ` Mauro Carvalho Chehab
2023-02-01 23:12 ` Stefan Herdler
2023-02-02 9:43 ` Soeren Moch
2023-02-02 21:26 ` Stefan Herdler
2023-02-03 0:58 ` Stefan Herdler
2023-02-03 8:50 ` Hans Verkuil
2023-02-06 0:06 ` Stefan Herdler
2023-02-08 9:08 ` Mauro Carvalho Chehab
2023-02-12 23:10 ` Stefan Herdler
2023-03-24 10:37 ` saa7146: please test the vb2 conversion! Hans Verkuil
2023-03-24 10:40 ` Hans Verkuil
2023-03-24 21:21 ` Stefan Herdler
2023-03-27 17:13 ` Tomasz Maciej Nowak
2023-04-06 22:43 ` Stefan Herdler
2023-04-07 7:04 ` Hans Verkuil
2023-04-09 22:36 ` Stefan Herdler
2023-04-11 7:29 ` Hans Verkuil
2023-04-12 10:11 ` Hans Verkuil
2023-04-12 11:16 ` Hans Verkuil
2023-04-14 0:15 ` Stefan Herdler
2023-04-14 8:36 ` Hans Verkuil
2023-04-15 21:15 ` Stefan Herdler
2023-03-25 1:44 ` [PATCH] Legacy DVB API: completion of documentation Stefan Herdler
2023-03-25 8:47 ` kernel test robot
2023-03-26 21:34 ` [PATCH v2] " Stefan Herdler
2023-03-27 18:28 ` Mauro Carvalho Chehab
2023-04-02 22:25 ` Stefan Herdler [this message]
2023-07-17 2:04 ` [PATCH v3 0/6] " Stefan Herdler
2023-07-17 2:04 ` [PATCH v3 1/6] Add documentation for legacy DVB decoder API Stefan Herdler
2023-07-17 2:04 ` [PATCH v3 2/6] Add documentation for osd.h Stefan Herdler
2023-07-17 2:04 ` [PATCH v3 3/6] Add documentation for audio.h (data types) Stefan Herdler
2023-07-19 9:09 ` kernel test robot
2023-07-17 2:04 ` [PATCH v3 4/6] Add documentation for audio.h (function calls) Stefan Herdler
2023-07-17 2:04 ` [PATCH v3 5/6] Add documentation for video.h (data types) Stefan Herdler
2023-07-17 2:04 ` [PATCH v3 6/6] Add documentation for video.h (function calls) Stefan Herdler
2024-01-28 23:32 ` [PATCH v4 0/6] media: docs: uAPI: dvb/decoder: completing the documentation Stefan Herdler
2024-01-28 23:32 ` [PATCH v4 1/6] " Stefan Herdler
2024-01-28 23:32 ` [PATCH v4 2/6] media: docs: uAPI: dvb/osd: " Stefan Herdler
2024-01-28 23:32 ` [PATCH v4 3/6] media: docs: uAPI: dvb/audio: completing the documentation (data types) Stefan Herdler
2024-01-28 23:32 ` [PATCH v4 4/6] media: docs: uAPI: dvb/audio: completing the documentation (function calls) Stefan Herdler
2024-01-28 23:32 ` [PATCH v4 5/6] media: docs: uAPI: dvb/video: completing the documentation (data types) Stefan Herdler
2024-01-28 23:32 ` [PATCH v4 6/6] media: docs: uAPI: dvb/video: completing the documentation (function calls) Stefan Herdler
2024-02-07 5:10 ` [PATCH v4 0/6] media: docs: uAPI: dvb/decoder: completing the documentation Mauro Carvalho Chehab
2024-02-08 23:56 ` Stefan Herdler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5b5a1dc0-96c4-c3c4-a24b-1917b39f8292@nurfuerspam.de \
--to=herdler@nurfuerspam.de \
--cc=abraham.manu@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=smoch@web.de \
--cc=tmn505@gmail.com \
--cc=vinschen@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).