From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Brad Smith <brad@comstyle.com>
Subject: Re: [FFmpeg-devel] [PATCH] avutil/ppc/cpu: Also use the machdep.altivec sysctl on NetBSD
Date: Sat, 11 May 2024 23:49:15 +0200
Message-ID: <20240511214915.GT6420@pb2> (raw)
In-Reply-To: <01af1809-98c6-43a5-b868-5e3ea1ff4103@comstyle.com>
[-- Attachment #1.1: Type: text/plain, Size: 1311 bytes --]
On Sat, May 11, 2024 at 03:55:44PM -0400, Brad Smith wrote:
> On 2024-05-06 10:24 p.m., Michael Niedermayer wrote:
> > On Sun, May 05, 2024 at 11:21:58PM -0400, Brad Smith wrote:
> > > avutil/ppc/cpu: Also use the machdep.altivec sysctl on NetBSD
> > >
> > > Use the machdep.altivec sysctl on NetBSD for AltiVec detection
> > > as is done with OpenBSD.
> > >
> > > Signed-off-by: Brad Smith<brad@comstyle.com>
> > > ---
> > > libavutil/ppc/cpu.c | 6 +++---
> > > 1 file changed, 3 insertions(+), 3 deletions(-)
> > you seem to be sending alot of bsd related patches, maybe
> > you want to send a patch that adds you to the MAINTAINERs file?
> >
> > thx
>
> I try to help where I can. I am an OpenBSD developer and take a look at
> what the other *BSD's have for local patches and push things upstream to
> benefit both sides, but I am not sure I have enough time to be in a position
> to be considered any kind of official MAINTAINER.
Iam not asking you to do more work
Id like to give you a git write account so you can push your BSD related
fixes yourself.
(everyone who has git write should be in MAINTAINERs)
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Avoid a single point of failure, be that a person or equipment.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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:[~2024-05-11 21:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 3:21 Brad Smith
2024-05-06 14:15 ` Sean McGovern
2024-05-07 2:24 ` Michael Niedermayer
2024-05-11 19:55 ` Brad Smith
2024-05-11 21:49 ` Michael Niedermayer [this message]
2024-05-11 22:24 ` Brad Smith
2024-05-12 0:13 ` Michael Niedermayer
2024-05-12 0:15 ` Brad Smith
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=20240511214915.GT6420@pb2 \
--to=michael@niedermayer.cc \
--cc=brad@comstyle.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