devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@collabora.com>
To: Hugh Cole-Baker <sigmaris@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Hans Verkuil <hans.verkuil@cisco.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Sakari Ailus <sakari.ailus@iki.fi>,
	linux-media@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, Tomasz Figa <tfiga@chromium.org>,
	Heiko Stuebner <heiko@sntech.de>, Jonas Karlman <jonas@kwiboo.se>,
	Nicolas Dufresne <nicolas@ndufresne.ca>,
	Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
	linux-rockchip@lists.infradead.org,
	Rob Herring <robh+dt@kernel.org>,
	kernel@collabora.com, Ezequiel Garcia <ezequiel@collabora.com>
Subject: Re: [PATCH v3 4/7] media: hantro: h264: Use the generic H264 reflist builder
Date: Mon, 16 Dec 2019 09:54:19 +0100	[thread overview]
Message-ID: <20191216095419.4dfb8501@collabora.com> (raw)
In-Reply-To: <24EFC68C-CF34-4D6E-8927-1CFA0CE81F45@gmail.com>

On Sat, 14 Dec 2019 15:46:35 +0000
Hugh Cole-Baker <sigmaris@gmail.com> wrote:

> Hi Boris,
> 
> > On 13 Dec 2019, at 12:54, Boris Brezillon <boris.brezillon@collabora.com> wrote:
> > 
> > Now that the core provides generic reflist builders, we can use them
> > instead of implementing our own.
> > 
> > Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>
> > ---
> > Changes in v3:
> > * New patch
> > ---
> > drivers/staging/media/hantro/hantro_h264.c | 237 +--------------------
> > 1 file changed, 8 insertions(+), 229 deletions(-)
> > 
> > diff --git a/drivers/staging/media/hantro/hantro_h264.c b/drivers/staging/media/hantro/hantro_h264.c
> > index 568640eab3a6..d998272d20e6 100644
> > --- a/drivers/staging/media/hantro/hantro_h264.c
> > +++ b/drivers/staging/media/hantro/hantro_h264.c
> > @@ -11,7 +11,7 @@
> >  */
> > 
> > #include <linux/types.h>
> > -#include <linux/sort.h>
> > +#include <media/v4l2-h264.h>  
> 
> With this patch, CONFIG_VIDEO_HANTRO needs to depend on CONFIG_V4L2_H264,
> without that it can encounter linking errors due to missing symbols for
> v4l2_h264_init_reflist_builder, etc.

Oops, you're right (I didn't notice it since I had it selected by
CONFIG_VIDEO_ROCKCHIP_VDEC). I'll fix that in v4.

Thanks,

Boris

  reply	other threads:[~2019-12-16  8:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-13 12:54 [PATCH v3 0/7] media: rockchip: Add the rkvdec driver Boris Brezillon
2019-12-13 12:54 ` [PATCH v3 1/7] media: vb2: Add a helper to get the vb2 buffer attached to a request Boris Brezillon
2019-12-13 15:09   ` Laurent Pinchart
2019-12-13 15:21     ` Boris Brezillon
2019-12-13 12:54 ` [PATCH v3 2/7] media: uapi: h264: Add DPB entry field reference flags Boris Brezillon
2019-12-13 12:54 ` [PATCH v3 3/7] media: v4l2-core: Add helpers to build the H264 P/B0/B1 reflists Boris Brezillon
2019-12-13 12:54 ` [PATCH v3 4/7] media: hantro: h264: Use the generic H264 reflist builder Boris Brezillon
2019-12-14 15:46   ` Hugh Cole-Baker
2019-12-16  8:54     ` Boris Brezillon [this message]
2019-12-13 12:54 ` [PATCH v3 5/7] media: dt-bindings: rockchip: Document RK3399 Video Decoder bindings Boris Brezillon
2019-12-13 15:23   ` Laurent Pinchart
2019-12-13 15:25     ` Boris Brezillon
2019-12-14  2:32       ` Chen-Yu Tsai
2019-12-18 22:03   ` Rob Herring
2019-12-13 12:54 ` [PATCH v3 6/7] media: rkvdec: Add the rkvdec driver Boris Brezillon
2019-12-13 14:21   ` Hans Verkuil
2019-12-13 15:05     ` Boris Brezillon
2020-01-06  7:52   ` Boris Brezillon
2019-12-13 12:54 ` [PATCH v3 7/7] arm64: dts: rockchip: rk3399: Define the rockchip Video Decoder node 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=20191216095419.4dfb8501@collabora.com \
    --to=boris.brezillon@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=ezequiel@collabora.com \
    --cc=hans.verkuil@cisco.com \
    --cc=heiko@sntech.de \
    --cc=jonas@kwiboo.se \
    --cc=kernel@collabora.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=mchehab@kernel.org \
    --cc=nicolas@ndufresne.ca \
    --cc=paul.kocialkowski@bootlin.com \
    --cc=robh+dt@kernel.org \
    --cc=sakari.ailus@iki.fi \
    --cc=sigmaris@gmail.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).