From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Michael Tretter <m.tretter@pengutronix.de>
Subject: Re: [GIT PULL FOR v5.3] Add ZynqMP VCU/Allegro DVT H.264 encoder driver
Date: Wed, 29 May 2019 08:07:13 -0300 [thread overview]
Message-ID: <20190529080713.03f47ab8@coco.lan> (raw)
In-Reply-To: <4d45c05b-8b24-6f35-a891-4646c8e1e1f5@xs4all.nl>
Em Tue, 28 May 2019 20:10:27 +0200
Hans Verkuil <hverkuil@xs4all.nl> escreveu:
> The following changes since commit 9bec226d8c79fcbc95817b082557f72a79d182f5:
>
> media: v4l2-pci-skeleton.c: fix doc warning (2019-05-28 13:14:28 -0400)
>
> are available in the Git repository at:
>
> git://linuxtv.org/hverkuil/media_tree.git tags/br-v5.3f
>
> for you to fetch changes up to 75e52767fa3d58a783dd6862a7fb686e5de67fc6:
>
> allegro: add SPS/PPS nal unit writer (2019-05-28 20:00:26 +0200)
>
> ----------------------------------------------------------------
> Tag branch
>
> ----------------------------------------------------------------
> Hans Verkuil (1):
> videobuf2-v4l2: set last_buffer_dequeued in dqbuf
>
> Michael Tretter (4):
> media: dt-bindings: media: document allegro-dvt bindings
> media: dt-bindings: media: Add vendor prefix for allegro
> allegro: add Allegro DVT video IP core driver
> allegro: add SPS/PPS nal unit writer
As this is staging, merged, but there's something wrong with DT here:
WARNING: DT compatible string vendor "allegro" appears un-documented -- check ./Documentation/devicetree/bindings/vendor-prefixes.yaml
#3013: FILE: drivers/staging/media/allegro-dvt/allegro-core.c:3013:
+ { .compatible = "allegro,al5e-1.1" },
Please send a followup patch addressing it.
Thanks,
Mauro
next prev parent reply other threads:[~2019-05-29 11:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 18:10 [GIT PULL FOR v5.3] Add ZynqMP VCU/Allegro DVT H.264 encoder driver Hans Verkuil
2019-05-29 11:07 ` Mauro Carvalho Chehab [this message]
2019-05-29 11:29 ` Hans Verkuil
2019-05-29 11:32 ` Hans Verkuil
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=20190529080713.03f47ab8@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=m.tretter@pengutronix.de \
/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.