From: Hans Verkuil <hverkuil@xs4all.nl>
To: Dafna Hirschfeld <dafna.hirschfeld@collabora.com>,
linux-media@vger.kernel.org
Cc: laurent.pinchart@ideasonboard.com, helen.koike@collabora.com,
ezequiel@collabora.com, kernel@collabora.com, dafna3@gmail.com,
sakari.ailus@linux.intel.com, linux-rockchip@lists.infradead.org,
mchehab@kernel.org, tfiga@chromium.org
Subject: Re: [PATCH v2 0/2] media: admin-guide: add documentation for rkisp1
Date: Thu, 17 Sep 2020 12:52:31 +0200 [thread overview]
Message-ID: <f696e967-ce1f-e7c1-a74b-ff944332bd67@xs4all.nl> (raw)
In-Reply-To: <20200818102703.30471-1-dafna.hirschfeld@collabora.com>
On 18/08/2020 12:27, Dafna Hirschfeld wrote:
> Two patches that document the rkisp1 driver in the Documentation
> directory.
>
> patch 1 adds documentation to the specific metadata formats
> used by the driver.
>
> patch 2 adds a documentation of the driver.
>
> The documentation assumes that the patchsets:
>
> "v4l2: add support for colorspace conversion API (CSC) for video capture and subdevices"
> https://patchwork.kernel.org/project/linux-media/list/?series=334393
>
> "media: staging: rkisp1: add support to V4L2_CAP_IO_MC"
> https://patchwork.kernel.org/cover/11680993/
The MAINTAINERS file needs to be updated for these new doc files. Just post a new patch for
this, no need for a v3.
Regards,
Hans
>
> were accepted and it documents the features that those patchsets add.
>
> changes from v1:
> ----------------
> - limit lines within 80 chars
> - rephrasing and fixing issues due to comments
>
> Dafna Hirschfeld (2):
> media: pixfmt-meta-rkisp1.rst: add description of rkisp1 metadata
> formats in pixfmt-meta-rkisp1.rst
> media: admin-guide: add documentation file rkisp1.rst
>
> Documentation/admin-guide/media/rkisp1.dot | 18 ++
> Documentation/admin-guide/media/rkisp1.rst | 181 ++++++++++++++++++
> .../admin-guide/media/v4l-drivers.rst | 1 +
> .../userspace-api/media/v4l/meta-formats.rst | 1 +
> .../media/v4l/pixfmt-meta-rkisp1.rst | 49 +++++
> .../uapi/v4l/pixfmt-meta-rkisp1-params.rst | 23 ---
> .../uapi/v4l/pixfmt-meta-rkisp1-stat.rst | 22 ---
> 7 files changed, 250 insertions(+), 45 deletions(-)
> create mode 100644 Documentation/admin-guide/media/rkisp1.dot
> create mode 100644 Documentation/admin-guide/media/rkisp1.rst
> create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-meta-rkisp1.rst
> delete mode 100644 drivers/staging/media/rkisp1/Documentation/media/uapi/v4l/pixfmt-meta-rkisp1-params.rst
> delete mode 100644 drivers/staging/media/rkisp1/Documentation/media/uapi/v4l/pixfmt-meta-rkisp1-stat.rst
>
next prev parent reply other threads:[~2020-09-17 10:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 10:27 [PATCH v2 0/2] media: admin-guide: add documentation for rkisp1 Dafna Hirschfeld
2020-08-18 10:27 ` [PATCH v2 1/2] media: pixfmt-meta-rkisp1.rst: add description of rkisp1 metadata formats in pixfmt-meta-rkisp1.rst Dafna Hirschfeld
2020-08-25 13:04 ` Helen Koike
2020-08-18 10:27 ` [PATCH v2 2/2] media: admin-guide: add documentation file rkisp1.rst Dafna Hirschfeld
2020-08-25 13:04 ` Helen Koike
2020-09-17 10:52 ` Hans Verkuil [this message]
2020-09-17 15:06 ` [PATCH v2 0/2] media: admin-guide: add documentation for rkisp1 Dafna Hirschfeld
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=f696e967-ce1f-e7c1-a74b-ff944332bd67@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=dafna.hirschfeld@collabora.com \
--cc=dafna3@gmail.com \
--cc=ezequiel@collabora.com \
--cc=helen.koike@collabora.com \
--cc=kernel@collabora.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tfiga@chromium.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 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).