From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Cc: linux-media@vger.kernel.org, Ezequiel Garcia <ezequiel@collabora.com>
Subject: Re: [PATCH 5/6] vidioc-g-ext-ctrls.rst: add missing 'struct' before the types
Date: Thu, 3 Dec 2020 13:07:43 +0100 [thread overview]
Message-ID: <20201203130743.1a6a62ca@coco.lan> (raw)
In-Reply-To: <66240aa3-1916-dd7d-83bc-367dc8675c40@xs4all.nl>
Em Thu, 3 Dec 2020 11:52:29 +0100
Hans Verkuil <hverkuil-cisco@xs4all.nl> escreveu:
> On 03/12/2020 11:49, Mauro Carvalho Chehab wrote:
> > Em Thu, 26 Nov 2020 14:27:16 +0100
> > Hans Verkuil <hverkuil-cisco@xs4all.nl> escreveu:
> >
> >> Add 'struct' to clarify that these are pointers to structs.
> >
> > This patch is actually wrong :-)
> >
> > It is incompatible with Sphinx 3.
> >
> >>
> >> Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
> >> ---
> >> .../userspace-api/media/v4l/vidioc-g-ext-ctrls.rst | 14 +++++++-------
> >> 1 file changed, 7 insertions(+), 7 deletions(-)
> >>
> >> diff --git a/Documentation/userspace-api/media/v4l/vidioc-g-ext-ctrls.rst b/Documentation/userspace-api/media/v4l/vidioc-g-ext-ctrls.rst
> >> index 726d6a97325f..5b1fc62ade0d 100644
> >> --- a/Documentation/userspace-api/media/v4l/vidioc-g-ext-ctrls.rst
> >> +++ b/Documentation/userspace-api/media/v4l/vidioc-g-ext-ctrls.rst
> >> @@ -180,31 +180,31 @@ still cause this situation.
> >> - ``p_u32``
> >> - A pointer to a matrix control of unsigned 32-bit values. Valid if
> >> this control is of type ``V4L2_CTRL_TYPE_U32``.
> >> - * - :c:type:`v4l2_area` *
> >> + * - struct :c:type:`v4l2_area` *
> >
> >
> > See, with Sphinx 3, :c:type: can only be used for typedefs and defines.
> >
> > The right markup for struct is:
> >
> > :c:struct:
> >
> > Actually, due to automarkup.py extension, I would just rename them to:
> >
> > struct foo
> >
> > And let the automarkup code to use the right markup, as it will ensure
> > that the proper dialect will be used, no matter what Sphinx version
> > will be used to produce the docs.
> >
> > So, I'll drop this patch from the series. I'll propose a new one
> > instead, after testing with multiple versions of Sphinx.
>
> 'git grep struct.*:c:type Documentation' shows a lot of those incorrect
> markups. Perhaps make a media-wide patch to fix this? Otherwise people
> will just keep copy-and-pasting the same incorrect markup.
Hmm... looking at Documentation/sphinx/parse-headers.pl, it seems
that the logic is not declaring structs using a Sphinx3 compatible
format, but, instead, using :c:type: everywhere.
So, I guess I'll just merge those two patches as-is, and then
work on a media-wide patchset.
>
> Regards,
>
> Hans
>
> >
> > Regards,
> > Mauro
> >
> >
> >
> >> - ``p_area``
> >> - A pointer to a struct :c:type:`v4l2_area`. Valid if this control is
> >> of type ``V4L2_CTRL_TYPE_AREA``.
> >> - * - :c:type:`v4l2_ctrl_h264_sps` *
> >> + * - struct :c:type:`v4l2_ctrl_h264_sps` *
> >> - ``p_h264_sps``
> >> - A pointer to a struct :c:type:`v4l2_ctrl_h264_sps`. Valid if this control is
> >> of type ``V4L2_CTRL_TYPE_H264_SPS``.
> >> - * - :c:type:`v4l2_ctrl_h264_pps` *
> >> + * - struct :c:type:`v4l2_ctrl_h264_pps` *
> >> - ``p_h264_pps``
> >> - A pointer to a struct :c:type:`v4l2_ctrl_h264_pps`. Valid if this control is
> >> of type ``V4L2_CTRL_TYPE_H264_PPS``.
> >> - * - :c:type:`v4l2_ctrl_h264_scaling_matrix` *
> >> + * - struct :c:type:`v4l2_ctrl_h264_scaling_matrix` *
> >> - ``p_h264_scaling_matrix``
> >> - A pointer to a struct :c:type:`v4l2_ctrl_h264_scaling_matrix`. Valid if this control is
> >> of type ``V4L2_CTRL_TYPE_H264_SCALING_MATRIX``.
> >> - * - :c:type:`v4l2_ctrl_h264_pred_weights` *
> >> + * - struct :c:type:`v4l2_ctrl_h264_pred_weights` *
> >> - ``p_h264_pred_weights``
> >> - A pointer to a struct :c:type:`v4l2_ctrl_h264_pred_weights`. Valid if this control is
> >> of type ``V4L2_CTRL_TYPE_H264_PRED_WEIGHTS``.
> >> - * - :c:type:`v4l2_ctrl_h264_slice_params` *
> >> + * - struct :c:type:`v4l2_ctrl_h264_slice_params` *
> >> - ``p_h264_slice_params``
> >> - A pointer to a struct :c:type:`v4l2_ctrl_h264_slice_params`. Valid if this control is
> >> of type ``V4L2_CTRL_TYPE_H264_SLICE_PARAMS``.
> >> - * - :c:type:`v4l2_ctrl_h264_decode_params` *
> >> + * - struct :c:type:`v4l2_ctrl_h264_decode_params` *
> >> - ``p_h264_decode_params``
> >> - A pointer to a struct :c:type:`v4l2_ctrl_h264_decode_params`. Valid if this control is
> >> of type ``V4L2_CTRL_TYPE_H264_DECODE_PARAMS``.
> >
> >
> >
> > Thanks,
> > Mauro
> >
>
Thanks,
Mauro
next prev parent reply other threads:[~2020-12-03 12:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 13:27 [PATCH 0/6] Stateless FWHT de-staging Hans Verkuil
2020-11-26 13:27 ` [PATCH 1/6] vicodec: add V4L2_ prefix before FWHT_VERSION and FWHT_FL_* Hans Verkuil
2020-11-26 13:27 ` [PATCH 2/6] vicodec: mark the stateless FWHT API as stable Hans Verkuil
2020-11-26 13:27 ` [PATCH 3/6] ext-ctrls-codec.rst: move FWHT docs to ext-ctrls-codec-stateless.rst Hans Verkuil
2020-11-26 13:27 ` [PATCH 4/6] pixfmt-compressed.rst: fix 'bullet' formatting Hans Verkuil
2020-11-26 13:27 ` [PATCH 5/6] vidioc-g-ext-ctrls.rst: add missing 'struct' before the types Hans Verkuil
2020-12-03 10:49 ` Mauro Carvalho Chehab
2020-12-03 10:52 ` Hans Verkuil
2020-12-03 12:07 ` Mauro Carvalho Chehab [this message]
2020-11-26 13:27 ` [PATCH 6/6] userspace-api/media: finalize stateless FWHT codec docs Hans Verkuil
2020-12-03 10:50 ` Mauro Carvalho Chehab
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=20201203130743.1a6a62ca@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=ezequiel@collabora.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-media@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.