From: "Guo, Yejun" <yejun.guo-at-intel.com@ffmpeg.org>
To: FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>,
"wenbin.chen-at-intel.com@ffmpeg.org"
<wenbin.chen-at-intel.com@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v6] libavfi/dnn: add LibTorch as one of DNN backend
Date: Fri, 15 Mar 2024 07:56:19 +0000
Message-ID: <PH7PR11MB59574F83C5A2532CE3CD6496F1282@PH7PR11MB5957.namprd11.prod.outlook.com> (raw)
In-Reply-To: <e5e58d61-1244-4765-a6f5-323746421a49@betaapp.fastmail.com>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Jean-
> Baptiste Kempf
> Sent: Friday, March 15, 2024 3:05 PM
> To: wenbin.chen-at-intel.com@ffmpeg.org; ffmpeg-devel <ffmpeg-
> devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH v6] libavfi/dnn: add LibTorch as one of
> DNN backend
>
> On Fri, 15 Mar 2024, at 05:42, wenbin.chen-at-intel.com@ffmpeg.org wrote:
> > From: Wenbin Chen <wenbin.chen@intel.com>
> >
> > PyTorch is an open source machine learning framework that accelerates
> > the path from research prototyping to production deployment. Official
> > website: https://pytorch.org/. We call the C++ library of PyTorch as
> > LibTorch, the same below.
>
> LGTM. Please apply.
Cool, I plan to have a clean try next week and then apply the patch, hope not too late.
_______________________________________________
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-03-15 7:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 4:42 wenbin.chen-at-intel.com
2024-03-15 7:05 ` Jean-Baptiste Kempf
2024-03-15 7:56 ` Guo, Yejun [this message]
2024-03-19 10:33 ` Guo, Yejun
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=PH7PR11MB59574F83C5A2532CE3CD6496F1282@PH7PR11MB5957.namprd11.prod.outlook.com \
--to=yejun.guo-at-intel.com@ffmpeg.org \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=wenbin.chen-at-intel.com@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