Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Emma Worley <emma@emma.gg>
To: Kacper Michajlow <kasper93@gmail.com>
Cc: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v5 3/3] lavc/dxvenc: improve compatibility with Resolume products
Date: Sun, 15 Jun 2025 15:24:59 -0700
Message-ID: <CAFQzNw6DGcxLDwDbwkLmKp5TSiuo-W0uBPW5Vz_8dWgk1AFQyQ@mail.gmail.com> (raw)
In-Reply-To: <CAFQzNw4kj7MqDayUijWbpb9G5a6AeUdeXoJzPDJh9GDCGrPv=w@mail.gmail.com>

I wasn't able to repro in a windows 11 arm64 VM. It seems the builds at
fate.ffmpeg.org are also unaffected.
_______________________________________________
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-15 22:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-25 16:05 [FFmpeg-devel] [PATCH v5 1/3] lavc/hashtable: create generic robin hood hash table Emma Worley
2025-04-25 16:05 ` [FFmpeg-devel] [PATCH v5 2/3] lavc/dxvenc: migrate DXT1 encoder to lavc hashtable Emma Worley
2025-04-25 16:05 ` [FFmpeg-devel] [PATCH v5 3/3] lavc/dxvenc: improve compatibility with Resolume products Emma Worley
2025-04-27  1:37   ` Emma Worley
2025-05-01  6:56     ` Emma Worley
2025-05-14  4:39       ` Emma Worley
2025-05-28 22:35         ` Emma Worley
2025-05-30 19:18           ` Michael Niedermayer
2025-05-31 23:42             ` Emma Worley
2025-06-14 23:00   ` Kacper Michajlow
2025-06-15  4:27     ` Emma Worley
2025-06-15 22:24       ` Emma Worley [this message]
2025-06-17 16:48         ` Kacper Michajlow
2025-05-30 19:23 ` [FFmpeg-devel] [PATCH v5 1/3] lavc/hashtable: create generic robin hood hash table Michael Niedermayer

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=CAFQzNw6DGcxLDwDbwkLmKp5TSiuo-W0uBPW5Vz_8dWgk1AFQyQ@mail.gmail.com \
    --to=emma@emma.gg \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=kasper93@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