From: Hans Verkuil <hverkuil@xs4all.nl>
To: Sakari Ailus <sakari.ailus@linux.intel.com>, linux-media@vger.kernel.org
Cc: laurent.pinchart@ideasonboard.com
Subject: Re: [v4l-utils PATCH v2 0/3] List supported formats in libv4l2subdev
Date: Fri, 22 Jan 2016 13:15:08 +0100 [thread overview]
Message-ID: <56A21D4C.4010800@xs4all.nl> (raw)
In-Reply-To: <1449587716-22954-1-git-send-email-sakari.ailus@linux.intel.com>
Hi Sakari,
Can you respin this series and add the "v4l: libv4l2subdev: Precisely convert
media bus string to code" patch to it as well? And incorporate Laurent's
comments?
I think this is a very useful addition and since Laurent's comments are minor
I suspect a v3 would be ready for merging.
Regards,
Hans
On 12/08/2015 04:15 PM, Sakari Ailus wrote:
> Hi,
>
> Rebased on current v4l-utils. There were conflicts as new media bus
> formats were added. The earlier version is here:
>
> <URL:http://www.spinics.net/lists/linux-media/msg94619.html>
>
> These patches go on top of the field support set, which hasn't appeared in
> the archive yet. The earlier version is here:
>
> <URL:http://www.spinics.net/lists/linux-media/msg94605.html>
>
next prev parent reply other threads:[~2016-01-22 12:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 15:15 [v4l-utils PATCH v2 0/3] List supported formats in libv4l2subdev Sakari Ailus
2015-12-08 15:15 ` [v4l-utils PATCH v2 1/3] libv4l2subdev: Use generated format definitions " Sakari Ailus
2015-12-13 21:36 ` Laurent Pinchart
2015-12-08 15:15 ` [v4l-utils PATCH v2 2/3] libv4l2subdev: Add a function to list library supported pixel codes Sakari Ailus
2015-12-13 21:39 ` Laurent Pinchart
2016-01-22 12:23 ` Sakari Ailus
2016-01-22 13:36 ` Sakari Ailus
2016-01-24 20:27 ` Laurent Pinchart
2015-12-08 15:15 ` [v4l-utils PATCH v2 3/3] media-ctl: List supported media bus formats Sakari Ailus
2016-01-22 12:15 ` Hans Verkuil [this message]
2016-01-22 12:26 ` [v4l-utils PATCH v2 0/3] List supported formats in libv4l2subdev Sakari Ailus
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=56A21D4C.4010800@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
/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