[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251018075352.4f65fc94@sal.lan>
Date: Sat, 18 Oct 2025 07:53:52 -0300
From: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
To: Jonathan Corbet <corbet@....net>
Cc: Linux Doc Mailing List <linux-doc@...r.kernel.org>, Mauro Carvalho
Chehab <mchehab@...nel.org>, linux-kernel@...r.kernel.org,
linux-media@...r.kernel.org, Hans Verkuil <hverkuil@...all.nl>
Subject: Re: [PATCH 00/23] Fix media uAPI cross references
Hi Jon,
Em Fri, 17 Oct 2025 14:08:39 -0600
Jonathan Corbet <corbet@....net> escreveu:
> Mauro Carvalho Chehab <mchehab+huawei@...nel.org> writes:
>
> > In the past, media used Docbook to generate documentation, together
> > with some logic to ensure that cross-references would match the
> > actual defined uAPI.
> >
> > The rationale is that we wanted to automatically check for uAPI
> > documentation gaps.
> >
> > The same logic was migrated to Sphinx. Back then, broken links
> > were reported. However, recent versions of it and/or changes at
> > conf.py disabled such checks.
> >
> > The result is that several symbols are now not cross-referenced,
> > and we don't get warnings anymore when something breaks.
> >
> > This series consist on 2 parts:
> >
> > Part 1: extra patches to parse_data_structs.py and kernel_include.py;
> > Part 2: media documentation fixes.
> >
> > I'm not sure what's the best strategy to merge it, as some patches
> > belong to doc while others are media. So, they can be merged on
> > either one of the tree, or split on two series and merged in
> > separate or even being merged via a PR applied on both trees.
> >
> > IMO, the latter is the better strategy.
>
> OK, this series has been applied to -rc1 and is available in my
> media-uapi branch. I've also merged it into docs-next.
Thanks!
Merged on media-committers next branch as well:
https://gitlab.freedesktop.org/linux-media/media-committers/-/commit/8652359fc004cbadbf0e95692c1472caac6260c2
>
> Thanks,
>
> jon
Powered by blists - more mailing lists