From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: [GIT PULL FOR v4.6] VSP1 patches
Date: Fri, 19 Feb 2016 09:52:16 -0200 [thread overview]
Message-ID: <20160219095216.104eeccf@recife.lan> (raw)
In-Reply-To: <4317918.v13nm0kyWH@avalon>
Hi Laurent,
Em Wed, 10 Feb 2016 22:55:27 +0200
Laurent Pinchart <laurent.pinchart@ideasonboard.com> escreveu:
> Hi Mauro,
>
> The following changes since commit 85e91f80cfc6c626f9afe1a4ca66447b8fd74315:
>
> Merge tag 'v4.5-rc3' into patchwork (2016-02-09 08:56:42 -0200)
>
> are available in the git repository at:
>
> git://linuxtv.org/pinchartl/media.git vsp1/next
>
> for you to fetch changes up to 94889923211c7d2fa9d46762c7636f43820a1692:
>
> v4l: vsp1: Configure device based on IP version (2016-02-10 15:38:11 +0200)
Thanks, patches reviewed, tested and merged.
However, as we mentioned on IRC, this driver doesn't pass at the
v4l2-compliance, as it doesn't implement the mandatory
VIDIOC_ENUM_FMT ioctl, causing it to not work properly with tools like
v4l2-ctl and qv4l2.
Please fix it on a later patch.
> Could you please merge this in a stable branch that will be sent to Linus as-
> is for v4.6 ? I have a series of DRM/KMS driver patches that depend on this
> patch set and want to get them merged in v4.6 as well.
>
> All patches have been previously sent to the linux-media mailing list, and
> most included in the same pull request you've rejected for v4.5 as it
> conflicted with your work-in-progress media controller changes.
You can pass the branch "vsp1" to Daniel for it to base the DRM/KMS driver
patches.
Regards,
Mauro
--
Thanks,
Mauro
next prev parent reply other threads:[~2016-02-19 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 20:55 [GIT PULL FOR v4.6] VSP1 patches Laurent Pinchart
2016-02-19 11:52 ` Mauro Carvalho Chehab [this message]
2016-02-20 1:01 ` Laurent Pinchart
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=20160219095216.104eeccf@recife.lan \
--to=mchehab@osg.samsung.com \
--cc=daniel.vetter@ffwll.ch \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.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).