From: Philipp Zabel <p.zabel@pengutronix.de>
To: Jonas Karlman <jonas@kwiboo.se>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Ezequiel Garcia <ezequiel@collabora.com>,
Maxime Ripard <mripard@kernel.org>,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Jernej Skrabec <jernej.skrabec@siol.net>,
Boris Brezillon <boris.brezillon@collabora.com>,
Tomasz Figa <tfiga@chromium.org>,
Alexandre Courbot <acourbot@chromium.org>,
Nicolas Dufresne <nicolas@ndufresne.ca>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] media: cedrus: Use correct H264 8x8 scaling list
Date: Tue, 29 Oct 2019 12:22:09 +0100 [thread overview]
Message-ID: <b1a0089f9fb46af9c5091db5da4ff1c944bf878a.camel@pengutronix.de> (raw)
In-Reply-To: <HE1PR06MB4011189B5455E402FACE08C2AC610@HE1PR06MB4011.eurprd06.prod.outlook.com>
On Tue, 2019-10-29 at 00:00 +0000, Jonas Karlman wrote:
> Documentation now define the expected order of scaling lists,
> change to use correct indices.
>
> Fixes: 6eb9b758e307 ("media: cedrus: Add H264 decoding support")
> Signed-off-by: Jonas Karlman <jonas@kwiboo.se>
Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de>
regards
Philipp
next prev parent reply other threads:[~2019-10-29 11:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 23:59 [PATCH 0/3] media: uapi: h264: clarify expected scaling list order Jonas Karlman
2019-10-29 0:00 ` [PATCH 1/3] media: uapi: h264: clarify expected scaling_list_4x4/8x8 order Jonas Karlman
2019-10-29 11:22 ` Philipp Zabel
[not found] ` <20191029000033.13540-1-jonas@kwiboo.se>
2019-10-29 0:00 ` [PATCH 2/3] media: cedrus: Use correct H264 8x8 scaling list Jonas Karlman
2019-10-29 11:22 ` Philipp Zabel [this message]
2019-10-29 0:00 ` [PATCH v2 3/3] media: hantro: Do not reorder H264 " Jonas Karlman
2019-10-29 11:22 ` Philipp Zabel
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=b1a0089f9fb46af9c5091db5da4ff1c944bf878a.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=acourbot@chromium.org \
--cc=boris.brezillon@collabora.com \
--cc=ezequiel@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=jernej.skrabec@siol.net \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=mripard@kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=paul.kocialkowski@bootlin.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
all inboxes | Powered by JetHome®