Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marvin Scholz <epirat07-at-gmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/3] lavf: add and use AVRTCPSenderReport struct
Date: Sat, 28 Jun 2025 16:28:21 +0200
Message-ID: <8ED3A1CC-166E-4C0E-8A41-60A1150592EF@gmail.com> (raw)
In-Reply-To: <20250627215048.GK29660@pb2>



On 27 Jun 2025, at 23:50, Michael Niedermayer wrote:

> On Tue, Jun 24, 2025 at 08:02:01PM +0200, Marvin Scholz wrote:
>> This will be used in a future commit to expose the SR as side-data.
>> ---
>>  libavcodec/defs.h     | 14 ++++++++++++++
>>  libavformat/rtpdec.c  | 34 ++++++++++++++++++++--------------
>>  libavformat/rtpdec.h  |  4 ++--
>>  libavformat/rtspdec.c |  2 +-
>>  4 files changed, 37 insertions(+), 17 deletions(-)
>
> this seems not to apply
>

Indeed, sent a new version rebased on recent master.

> git am -3
> Applying: lavf: add and use AVRTCPSenderReport struct
> error: sha1 information is lacking or useless (libavformat/rtpdec.c).
> error: could not build fake ancestor
> Patch failed at 0001 lavf: add and use AVRTCPSenderReport struct
> hint: Use 'git am --show-current-patch=diff' to see the failed patch
> hint: When you have resolved this problem, run "git am --continue".
> hint: If you prefer to skip this patch, run "git am --skip" instead.
> hint: To restore the original branch and stop patching, run "git am --abort".
> hint: Disable this message with "git config set advice.mergeConflict false"
>
>
> git am --show-current-patch=diff | patch -p1 --dry-run  -F9
> checking file libavcodec/defs.h
> checking file libavformat/rtpdec.c
> Hunk #4 FAILED at 602.
> Hunk #5 FAILED at 622.
> 2 out of 5 hunks FAILED
> checking file libavformat/rtpdec.h
> checking file libavformat/rtspdec.c
>
>
> [...]
> -- 
> Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> Many things microsoft did are stupid, but not doing something just because
> microsoft did it is even more stupid. If everything ms did were stupid they
> would be bankrupt already.
> _______________________________________________
> 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".
_______________________________________________
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:[~2025-06-28 14:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24 18:02 [FFmpeg-devel] [PATCH 1/3] lavf/rtpdec: fix RTCP SR packet length check Marvin Scholz
2025-06-24 18:02 ` [FFmpeg-devel] [PATCH 2/3] lavf: add and use AVRTCPSenderReport struct Marvin Scholz
2025-06-27 21:50   ` Michael Niedermayer
2025-06-28 14:28     ` Marvin Scholz [this message]
2025-06-24 18:02 ` [FFmpeg-devel] [PATCH 3/3] lavf: add AV_PKT_DATA_RTCP_SR side data type Marvin Scholz
2025-06-28 14:27 ` [FFmpeg-devel] [PATCH v2 1/3] lavf/rtpdec: fix RTCP SR packet length check Marvin Scholz
2025-06-28 14:27   ` [FFmpeg-devel] [PATCH v2 2/3] lavf: add and use AVRTCPSenderReport struct Marvin Scholz
2025-06-28 14:27   ` [FFmpeg-devel] [PATCH v2 3/3] lavf: add AV_PKT_DATA_RTCP_SR side data type Marvin Scholz

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=8ED3A1CC-166E-4C0E-8A41-60A1150592EF@gmail.com \
    --to=epirat07-at-gmail.com@ffmpeg.org \
    --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