From: Andrzej Pietrasiewicz <andrzej.p@collabora.com>
To: Ezequiel Garcia <ezequiel@collabora.com>, devel@driverdev.osuosl.org
Cc: linux-media@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
kernel@collabora.com, Tomasz Figa <tfiga@chromium.org>
Subject: Re: [PATCH 0/4] Hantro VPU JPEG encoder fixes
Date: Fri, 7 Feb 2020 12:50:53 +0100 [thread overview]
Message-ID: <8a526fdb-cbfb-fe75-e24f-83f7c09a13a5@collabora.com> (raw)
In-Reply-To: <1d83a74c24269c7bcf6d6d8a789c88dbf7370dbb.camel@collabora.com>
Hi All,
<snip>
> I've just tested RK3288, and this series is indeed fixing
> these issues. So for all patches:
>
> Tested-by: Ezequiel Garcia <ezequiel@collabora.com>
A kind reminder.
The series fixes serious encoding quality problems in both rk3399 and rk3288,
so it seems it should be included. A review is needed, though, at least for
patches 2-4.
Thank you,
Andrzej
prev parent reply other threads:[~2020-02-07 11:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 14:30 [PATCH 0/4] Hantro VPU JPEG encoder fixes Andrzej Pietrasiewicz
2020-01-27 14:30 ` [PATCH 1/4] media: hantro: Read be32 words starting at every fourth byte Andrzej Pietrasiewicz
2020-01-27 18:26 ` Ezequiel Garcia
2020-01-27 14:30 ` [PATCH 2/4] media: hantro: Use standard luma quantization table Andrzej Pietrasiewicz
2020-01-27 19:46 ` Ezequiel Garcia
2020-01-27 14:30 ` [PATCH 3/4] media: hantro: Write the quantization tables in proper order Andrzej Pietrasiewicz
2020-01-27 14:30 ` [PATCH 4/4] media: hantro: Write quantization table registers in increasing addresses order Andrzej Pietrasiewicz
2020-01-27 18:11 ` [PATCH 0/4] Hantro VPU JPEG encoder fixes Ezequiel Garcia
2020-02-07 11:50 ` Andrzej Pietrasiewicz [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=8a526fdb-cbfb-fe75-e24f-83f7c09a13a5@collabora.com \
--to=andrzej.p@collabora.com \
--cc=devel@driverdev.osuosl.org \
--cc=ezequiel@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@collabora.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.