From: Ezequiel Garcia <ezequiel@collabora.com>
To: linux-media@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Tomasz Figa <tfiga@chromium.org>,
kernel@collabora.com, Jonas Karlman <jonas@kwiboo.se>,
Heiko Stuebner <heiko@sntech.de>,
Hans Verkuil <hverkuil@xs4all.nl>,
Alexandre Courbot <acourbot@chromium.org>,
Jeffrey Kardatzke <jkardatzke@chromium.org>,
gustavo.padovan@collabora.com,
Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Boris Brezillon <boris.brezillon@collabora.com>
Subject: Re: [PATCH 3/3] media: rkvdec: Add the VP9 backend
Date: Mon, 18 May 2020 14:53:44 -0300 [thread overview]
Message-ID: <65300f1bacda58e5752e27c781eb49de0198f56f.camel@collabora.com> (raw)
In-Reply-To: <20200518174011.15543-4-ezequiel@collabora.com>
On Mon, 2020-05-18 at 14:40 -0300, Ezequiel Garcia wrote:
> [PATCH 3/3] media: rkvdec: Add the VP9 backend
Oops, ^ should be v4 here.
Thanks,
Ezequiel
next prev parent reply other threads:[~2020-05-18 18:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 17:40 [PATCH v4 0/3] media: rkvdec: Add a VP9 backend Ezequiel Garcia
2020-05-18 17:40 ` [PATCH v4 1/3] media: rkvdec: Fix .buf_prepare Ezequiel Garcia
2020-05-20 13:07 ` Hans Verkuil
2020-05-20 13:12 ` Ezequiel Garcia
2020-05-18 17:40 ` [PATCH v4 2/3] media: uapi: Add VP9 stateless decoder controls Ezequiel Garcia
2020-05-20 13:26 ` Hans Verkuil
2020-09-10 6:04 ` Alexandre Courbot
2020-09-10 8:43 ` Alexandre Courbot
2021-02-24 21:07 ` Nicolas Dufresne
2021-02-28 6:13 ` Alexandre Courbot
2021-03-01 18:43 ` Nicolas Dufresne
2021-03-02 3:48 ` Alexandre Courbot
2020-05-18 17:40 ` [PATCH 3/3] media: rkvdec: Add the VP9 backend Ezequiel Garcia
2020-05-18 17:53 ` Ezequiel Garcia [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-13 13:31 [PATCH 0/3] media: rkvdec: Add a " Boris Brezillon
2019-12-13 13:31 ` [PATCH 3/3] media: rkvdec: Add the " Boris Brezillon
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=65300f1bacda58e5752e27c781eb49de0198f56f.camel@collabora.com \
--to=ezequiel@collabora.com \
--cc=acourbot@chromium.org \
--cc=boris.brezillon@collabora.com \
--cc=gustavo.padovan@collabora.com \
--cc=heiko@sntech.de \
--cc=hverkuil@xs4all.nl \
--cc=jkardatzke@chromium.org \
--cc=jonas@kwiboo.se \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=nicolas.dufresne@collabora.com \
--cc=tfiga@chromium.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).