Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Raphaël Zumer" <raphael.zumer@vimeo.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v4 2/2] avutil: add HDR10+ dynamic metadata serialization function
Date: Mon, 13 Mar 2023 16:53:35 -0400
Message-ID: <de40b3a0-9a6e-150d-f7a6-98500a6fbaed@vimeo.com> (raw)
In-Reply-To: <7197b4f6-37ce-4d8a-b8ef-0b175006e131@gmail.com>

On 3/13/23 16:47, James Almer wrote:
> On 3/13/2023 5:23 PM, Raphaël Zumer wrote:
>> Signed-off-by: Raphaël Zumer <rzumer@tebako.net>
>> ---
>>   doc/APIchanges                   |   5 ++
>>   libavutil/hdr_dynamic_metadata.c | 146 +++++++++++++++++++++++++++++++
>>   libavutil/hdr_dynamic_metadata.h |  12 +++
>>   libavutil/version.h              |   2 +-
>>   4 files changed, 164 insertions(+), 1 deletion(-)
> The serialization code here looks almost the same as the one submitted 
> some time ago by Mohammad Izadi in 
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/20220908012214.1556959-1-izadi@google.com/
> He in fact used the (int)(const AVDynamicHDRPlus* s, uint8_t** data, 
> size_t* size) signature for the function which does look more versatile 
> as it allows the return of error codes, fwiw.
>
> IMO, this patch should either have him as co-author, or a line added to 
> the commit message mentioning that it's based on his work.

I've actually never seen this code, but I agree that this is a better signature. I will fix that and add him as co-author.

RZ

_______________________________________________
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".

      reply	other threads:[~2023-03-13 20:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13 20:23 Raphaël Zumer
2023-03-13 20:47 ` James Almer
2023-03-13 20:53   ` Raphaël Zumer [this message]

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=de40b3a0-9a6e-150d-f7a6-98500a6fbaed@vimeo.com \
    --to=raphael.zumer@vimeo.com \
    --cc=ffmpeg-devel@ffmpeg.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

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