From: abenson <abenson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: ffmpeg: add option --enable-nvdec
Date: Wed, 24 Aug 2022 18:53:09 +0200 [thread overview]
Message-ID: <20220824165309.N4u2JCad_QWzOugH2B7uLV6I-fASVahoJLrNLMRgV5k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38829@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 615 bytes --]
There's a merged pull request on the void-packages repository
ffmpeg: add option --enable-nvdec
https://github.com/void-linux/void-packages/pull/38829
Description:
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64 (crossbuild)
- aarch64-musl (crossbuild)
- armv7l (crossbuild)
This is an update to try fixing issue #38782.
@nvidiaLinuxUser, could you please test this PR for your system?
prev parent reply other threads:[~2022-08-24 16:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 9:20 [PR PATCH] " dataCobra
2022-08-22 11:02 ` [PR REVIEW] " sgn
2022-08-22 11:03 ` sgn
2022-08-22 12:34 ` [PR PATCH] [Updated] " dataCobra
2022-08-22 12:37 ` [PR REVIEW] " dataCobra
2022-08-22 12:38 ` dataCobra
2022-08-22 13:01 ` nvidiaLinuxUser
2022-08-22 13:01 ` nvidiaLinuxUser
2022-08-22 13:01 ` nvidiaLinuxUser
2022-08-22 13:02 ` nvidiaLinuxUser
2022-08-22 14:03 ` nvidiaLinuxUser
2022-08-22 14:04 ` nvidiaLinuxUser
2022-08-22 14:05 ` nvidiaLinuxUser
2022-08-22 14:07 ` nvidiaLinuxUser
2022-08-23 0:00 ` sgn
2022-08-23 22:35 ` abenson
2022-08-24 5:47 ` dataCobra
2022-08-24 12:45 ` abenson
2022-08-24 12:48 ` abenson
2022-08-24 12:59 ` dataCobra
2022-08-24 16:02 ` sgn
2022-08-24 16:53 ` abenson [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=20220824165309.N4u2JCad_QWzOugH2B7uLV6I-fASVahoJLrNLMRgV5k@z \
--to=abenson@users.noreply.github.com \
--cc=ml@inbox.vuxu.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).