From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
To: ffmpegagent <ffmpegagent@gmail.com>,
"ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v3 0/2] Improve HWDeviceContext logging
Date: Sat, 19 Apr 2025 15:15:26 +0000
Message-ID: <DM8P223MB0365C5569F25254FA6C065D7BABE2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <pull.61.v3.ffstaging.FFmpeg.1745073799.ffmpegagent@gmail.com>
> -----Original Message-----
> From: ffmpegagent <ffmpegagent@gmail.com>
> Sent: Samstag, 19. April 2025 16:43
> To: ffmpeg-devel@ffmpeg.org
> Cc: softworkz <softworkz@hotmail.com>
> Subject: [PATCH v3 0/2] Improve HWDeviceContext logging
>
> This changeset
>
> * adds an av class category for hw device contexts
> * assigns a color to it
> * adds an item_name function to the av class for hw device context
>
>
> Before
> ======
>
> [AVHWDeviceContext @ 00000260A9C63E00] Selecting d3d11va adapter 2
> [AVHWDeviceContext @ 00000260A9C63E00] Using device 8086:4c8a
> (Intel(R) UH..
> [AVHWDeviceContext @ 00000260A9BFFC40] Use Intel(R) Media SDK to
> create MF..
> [AVHWDeviceContext @ 00000260A9BFFC40] Initialize MFX session:
> implementat..
> [h264 @ 00000260AC0DC640] Reinit context to 1920x800, pix_fmt: yuv420p
>
>
> After
> =====
>
> [D3D11VA @ 00000184942C25C0] Selecting d3d11va adapter 2
> [D3D11VA @ 00000184942C25C0] Using device 8086:4c8a (Intel(R) UHD
> Graphics..
> [QSV @ 00000184942601C0] Use Intel(R) Media SDK to create MFX session,
> API..
> [QSV @ 00000184942601C0] Initialize MFX session: implementation
> version is..
> [h264 @ 00000184964BA9C0] Reinit context to 1920x800, pix_fmt: yuv420p
>
> (..unable to show the terminal color change in plain text e-mail)
>
>
> V2
> ==
>
> * Resolved merge conflicts
> * PING
>
>
> V3
> ==
>
> TWO QUESTIONS BEFORE PUSHING:
>
> 1. Adding an enum member without affecting the value of the last
> member
> (_NB)
>
> =>Is that a MINOR or a MICRO version bump?
>
> 2. The date in doc/APIchanges
>
> => Should I adjust it to the date when pushing or keep the date it had
> in
> the submitted patchset?
>
From the history of APIChanges, most of the time - but not always - the
date appears to be set to the date when it's finally pushed, so I'll
go with that.
Could somebody please confirm the kind of version bump needed for this
specific case?
Thanks
sw
_______________________________________________
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:[~2025-04-19 15:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 5:37 [FFmpeg-devel] [PATCH " ffmpegagent
2025-03-12 5:37 ` [FFmpeg-devel] [PATCH 1/2] avutil/log, hwcontext: Add AV_CLASS_CATEGORY_HWDEVICE softworkz
2025-03-12 5:37 ` [FFmpeg-devel] [PATCH 2/2] avutil/hwcontext: Add item_name function for AVHWDeviceContext softworkz
2025-03-29 18:36 ` [FFmpeg-devel] [PATCH v2 0/2] Improve HWDeviceContext logging ffmpegagent
2025-03-29 18:36 ` [FFmpeg-devel] [PATCH v2 1/2] avutil/log, hwcontext: Add AV_CLASS_CATEGORY_HWDEVICE softworkz
2025-03-29 18:36 ` [FFmpeg-devel] [PATCH v2 2/2] avutil/hwcontext: Add item_name function for AVHWDeviceContext softworkz
2025-04-19 14:43 ` [FFmpeg-devel] [PATCH v3 0/2] Improve HWDeviceContext logging ffmpegagent
2025-04-19 14:43 ` [FFmpeg-devel] [PATCH v3 1/2] avutil/log, hwcontext: Add AV_CLASS_CATEGORY_HWDEVICE softworkz
2025-04-19 14:43 ` [FFmpeg-devel] [PATCH v3 2/2] avutil/hwcontext: Add item_name function for AVHWDeviceContext softworkz
2025-04-19 15:15 ` softworkz . [this message]
2025-04-20 23:17 ` [FFmpeg-devel] [PATCH v3 0/2] Improve HWDeviceContext logging Michael Niedermayer
2025-04-20 23:20 ` softworkz .
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=DM8P223MB0365C5569F25254FA6C065D7BABE2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz-at-hotmail.com@ffmpeg.org \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=ffmpegagent@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