From: Daniel Almeida <dwlsalmeida@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: andrzejtp2010@gmail.com, Frank Li <frank.li@nxp.com>,
ming.qian@oss.nxp.com, linux-media <linux-media@vger.kernel.org>,
Adam Ford <aford173@gmail.com>,
linux-imx@nxmp.com
Subject: Re: Hantro H1 Encoding Upstreaming
Date: Mon, 13 Jan 2025 17:38:37 -0300 [thread overview]
Message-ID: <F5E2D925-668C-4D4D-87C9-8F22126443FD@gmail.com> (raw)
In-Reply-To: <CAOMZO5BJt6qzETzMeO47N5Gu8136tppuXKnqv4ypk6HyLR99vA@mail.gmail.com>
Hi Fabio,
> On 13 Jan 2025, at 17:28, Fabio Estevam <festevam@gmail.com> wrote:
>
> [Resending because Andrzej's Collabora e-mail bounces]
>
> On Mon, Jan 13, 2025 at 5:25 PM Fabio Estevam <festevam@gmail.com> wrote:
>>
>> Hi Andrzej,
>>
>> Do you plan to submit a non-RFC of the Hantro Encoding patch series
>> that you submitted earlier?
>>
>> https://patchwork.kernel.org/project/linux-media/cover/20231116154816.70959-1-andrzej.p@collabora.com/
>>
>> I don't have access to the ST chip, but I am interested in using it on
>> the i.MX8MM and i.MX8MP.
>>
>> Please let me know.
>>
>> Thanks,
>>
>> Fabio Estevam
>
Andrzej doesn’t work for Collabora anymore.
— Daniel
next prev parent reply other threads:[~2025-01-13 20:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 20:25 Hantro H1 Encoding Upstreaming Fabio Estevam
2025-01-13 20:28 ` Fabio Estevam
2025-01-13 20:38 ` Daniel Almeida [this message]
2025-01-13 20:54 ` Adam Ford
2025-01-13 21:08 ` Daniel Almeida
2025-01-14 16:16 ` Nicolas Dufresne
2025-01-14 18:01 ` Andrzej Pietrasiewicz
2025-01-14 18:06 ` Nicolas Dufresne
2025-01-15 11:31 ` Adam Ford
2025-01-15 13:53 ` Michael Tretter
2025-01-15 15:03 ` Paul Kocialkowski
2025-01-15 19:43 ` Nicolas Dufresne
2025-01-18 16:49 ` Paul Kocialkowski
2025-01-15 19:51 ` Nicolas Dufresne
2025-01-18 17:00 ` Paul Kocialkowski
2025-01-15 20:14 ` Nicolas Dufresne
2025-01-18 17:15 ` Paul Kocialkowski
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=F5E2D925-668C-4D4D-87C9-8F22126443FD@gmail.com \
--to=dwlsalmeida@gmail.com \
--cc=aford173@gmail.com \
--cc=andrzejtp2010@gmail.com \
--cc=festevam@gmail.com \
--cc=frank.li@nxp.com \
--cc=linux-imx@nxmp.com \
--cc=linux-media@vger.kernel.org \
--cc=ming.qian@oss.nxp.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
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