From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Stefan Herdler <herdler@nurfuerspam.de>
Cc: hverkuil-cisco@xs4all.nl, linux-media@vger.kernel.org,
smoch@web.de, tmn505@gmail.com, vinschen@redhat.com
Subject: Re: [PATCH v4 0/6] media: docs: uAPI: dvb/decoder: completing the documentation
Date: Wed, 7 Feb 2024 06:10:20 +0100 [thread overview]
Message-ID: <20240207061020.0a6fa3bb@coco.lan> (raw)
In-Reply-To: <20240128233249.32794-1-herdler@nurfuerspam.de>
Hi Stefan,
Em Mon, 29 Jan 2024 00:32:43 +0100
Stefan Herdler <herdler@nurfuerspam.de> escreveu:
> This is basically a resend of v3 after 6 month, with some minor updates.
> Changes since v3:
> * Adjust title and description to better match existing documentation.
> * Fix warnings from kernel test robot.
> (At least I hope it is fixed now, I couldn't reproduce this warning.)
>
> No changes to the text it self.
> The layout is still identical since v1, just split into multiple patches.
> My comments of v3 attached below, they refer to Mauros comments[3] to
> v2 and still fully apply.
Patch series applied. I opted to reorder the series placing patch 1 at the
end, as otherwise it would cause bisect issues, as the index would be
trying to reference non-existing files.
Thank you for the series!
Regards,
Mauro
>
> [3: https://patchwork.kernel.org/project/linux-media/patch/decd5d71-f06e-5873-5ebf-7028107f65ee@nurfuerspam.de/]
>
>
> [PATCH v3] (July '23) ---------------------------------------------------
>
> Changes since v2:
> * Split the patch into a patch series.
> * Incorporate the changes requested.
> * Style updates to better match the existing documentation.
> * And a lot of small fixes.
>
>
> Hi Mauro,
>
> it took a little longer then expected, but I didn't had much time in spare
> for this. I'm pretty much occupied by other things at the moment.
> The winter season would be better for things like this, but I try to
> finish it as quick as possible.
>
> I went through your mail point by point and I'm confident, that I was able
> to sort out your questions now. At least I don't see anything that need to
> be improved anymore.
> The work has been done in a lot of small blocks over a pretty long period
> after my daily work, mostly late at night. Despite double checking
> everything, I maybe still have missed something. I hope it is not too
> much.
>
> For usage it has been checked against the known projects using the DVB
> decoder APIs:
> * The AV7110 kernel driver.
> * The out of tree driver for the HD full featured cards.[1]
> * The "Enigma2" sources from openatv team.[2]
> (The drivers of the boxes are binary only.)
>
> Possibly unused items have been listed in the comment of the patches.
> Please take this lists with a pinch of salt. With the number of items
> checked, it is pretty easy to miss an occurrence or have a false positive.
> Although I've done my best, there is still the chance that I've missed an
> use case.
>
> I tried to complete the documentation of this unused definition too.
> Most information had been collect anyway and writing it down wasn't that
> much of effort.
>
> Removing the definition and documentation later at once is always an
> option.
> I would prefer to do it this way, if something has to be removed.
> It is easier to revert the change in case of a regression.
> If necessary I can provide the patches too.
>
> Regards
> Stefan
>
> [1: https://github.com/s-moch/linux-saa716x]
> [2: https://github.com/openatv/enigma2/tree/master]
>
>
>
> Stefan Herdler (6):
> Add documentation for legacy DVB decoder API
> Add documentation for osd.h
> Add documentation for audio.h (data types)
> Add documentation for audio.h (function calls)
> Add documentation for video.h (data types)
> Add documentation for video.h (function calls)
>
> .../media/dvb/legacy_dvb_apis.rst | 1 +
> .../media/dvb/legacy_dvb_audio.rst | 1642 +++++++++++
> .../media/dvb/legacy_dvb_decoder_api.rst | 61 +
> .../media/dvb/legacy_dvb_osd.rst | 883 ++++++
> .../media/dvb/legacy_dvb_video.rst | 2430 +++++++++++++++++
> 5 files changed, 5017 insertions(+)
> create mode 100644 Documentation/userspace-api/media/dvb/legacy_dvb_audio.rst
> create mode 100644 Documentation/userspace-api/media/dvb/legacy_dvb_decoder_api.rst
> create mode 100644 Documentation/userspace-api/media/dvb/legacy_dvb_osd.rst
> create mode 100644 Documentation/userspace-api/media/dvb/legacy_dvb_video.rst
>
> --
> 2.34.0
>
>
Thanks,
Mauro
next prev parent reply other threads:[~2024-02-07 5:10 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
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 ` Mauro Carvalho Chehab [this message]
2024-02-08 23:56 ` [PATCH v4 0/6] media: docs: uAPI: dvb/decoder: completing the documentation 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=20240207061020.0a6fa3bb@coco.lan \
--to=mchehab@kernel.org \
--cc=herdler@nurfuerspam.de \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-media@vger.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).