From: "Ronald S. Bultje" <rsbultje@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Leo Izen <leo.izen@gmail.com>
Subject: Re: [FFmpeg-devel] [PATCH] avutil/csp: create public API for colorspace structs
Date: Fri, 13 May 2022 15:14:45 -0400
Message-ID: <CAEEMt2kyZWieTScu39tifx2YR_jpxMChQGxEPjy6UTSJhoDKiw@mail.gmail.com> (raw)
In-Reply-To: <20220513154208.17941-1-leo.izen@gmail.com>
Hi,
On Fri, May 13, 2022 at 11:42 AM Leo Izen <leo.izen@gmail.com> wrote:
> This commit moves some of the functionality from avfilter/colorspace
> into avutil/csp and exposes it as a public API so it can be used by
> libavcodec and/or libavformat.
> ---
> libavfilter/colorspace.c | 88 ----------------------------
> libavfilter/colorspace.h | 25 +-------
> libavfilter/fflcms2.c | 3 +-
> libavfilter/fflcms2.h | 2 +-
> libavfilter/vf_colorspace.c | 9 +--
> libavfilter/vf_iccdetect.c | 3 +-
> libavutil/Makefile | 2 +
> libavutil/csp.c | 111 ++++++++++++++++++++++++++++++++++++
> libavutil/csp.h | 49 ++++++++++++++++
> 9 files changed, 173 insertions(+), 119 deletions(-)
> create mode 100644 libavutil/csp.c
> create mode 100644 libavutil/csp.h
>
I don't have objections.
Ronald
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-05-13 19:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 15:42 Leo Izen
2022-05-13 19:14 ` Ronald S. Bultje [this message]
2022-05-13 19:18 ` James Almer
2022-05-14 2:43 ` Leo Izen
2022-05-13 21:22 ` Michael Niedermayer
2022-05-14 2:41 ` Leo Izen
2022-05-14 12:15 ` Niklas Haas
2022-05-15 16:49 ` Ronald S. Bultje
2022-05-15 18:10 ` Niklas Haas
2022-05-15 18:55 ` Michael Niedermayer
2022-05-15 19:19 ` Michael Niedermayer
2022-05-15 16:32 ` Andreas Rheinhardt
2022-05-16 14:45 ` Leo Izen
2022-05-18 12:21 ` Niklas Haas
2022-05-18 12:29 ` Niklas Haas
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=CAEEMt2kyZWieTScu39tifx2YR_jpxMChQGxEPjy6UTSJhoDKiw@mail.gmail.com \
--to=rsbultje@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=leo.izen@gmail.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git