public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: laurent.pinchart@ideasonboard.com, hverkuil@xs4all.nl
Subject: [v4l-utils PATCH 0/4] List supported formats in libv4l2subdev
Date: Sun, 21 Feb 2016 23:29:43 +0200	[thread overview]
Message-ID: <1456090187-1191-1-git-send-email-sakari.ailus@linux.intel.com> (raw)

Hi,

I've changed the patches according to comments from Laurent.

since v2:

- Remove the guardian (format code zero at the end of the list).

- v4l2_subdev_pixelcode_list() called only once pre printing the list.

-- 
Kind regards,
Sakari


             reply	other threads:[~2016-02-21 21:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-21 21:29 Sakari Ailus [this message]
2016-02-21 21:29 ` [v4l-utils PATCH 1/4] v4l: libv4lsubdev: Make mbus_formats array const Sakari Ailus
2016-02-21 21:29 ` [v4l-utils PATCH 2/4] libv4l2subdev: Use generated format definitions in libv4l2subdev Sakari Ailus
2016-02-21 21:29 ` [v4l-utils PATCH 3/4] libv4l2subdev: Add a function to list library supported pixel codes Sakari Ailus
2016-02-23 12:37   ` Hans Verkuil
2016-02-23 15:58     ` Sakari Ailus
2016-02-21 21:29 ` [v4l-utils PATCH 4/4] media-ctl: List supported media bus formats Sakari Ailus
2016-02-23 12:18   ` Hans Verkuil
2016-02-23 16:11     ` Sakari Ailus
2016-02-23 16:15       ` Hans Verkuil
2016-02-23 20:15         ` Laurent Pinchart
2016-02-23 20:24           ` Sakari Ailus
2016-02-23 20:30             ` Laurent Pinchart
2016-02-24  8:35               ` Sakari Ailus
2016-02-24 15:38               ` Hans Verkuil
2016-02-24 15:41                 ` Sakari Ailus
2016-02-24 15:44                 ` Sakari Ailus
2016-02-23 12:35   ` Hans Verkuil
  -- strict thread matches above, loose matches on Subject: below --
2015-11-09 13:25 [v4l-utils PATCH 0/4] 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=1456090187-1191-1-git-send-email-sakari.ailus@linux.intel.com \
    --to=sakari.ailus@linux.intel.com \
    --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