All of lore.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: [PATCH v5 1/4] v4l: libv4lsubdev: Make mbus_formats array const
Date: Wed, 24 Feb 2016 18:25:25 +0200	[thread overview]
Message-ID: <1456331128-7036-2-git-send-email-sakari.ailus@linux.intel.com> (raw)
In-Reply-To: <1456331128-7036-1-git-send-email-sakari.ailus@linux.intel.com>

The array is already static and may not be modified at runtime. Make it
const.

Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
---
 utils/media-ctl/libv4l2subdev.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/utils/media-ctl/libv4l2subdev.c b/utils/media-ctl/libv4l2subdev.c
index dc2cd87..e45834f 100644
--- a/utils/media-ctl/libv4l2subdev.c
+++ b/utils/media-ctl/libv4l2subdev.c
@@ -715,7 +715,7 @@ int v4l2_subdev_parse_setup_formats(struct media_device *media, const char *p)
 	return *end ? -EINVAL : 0;
 }
 
-static struct {
+static const struct {
 	const char *name;
 	enum v4l2_mbus_pixelcode code;
 } mbus_formats[] = {
-- 
2.1.0.231.g7484e3b


  reply	other threads:[~2016-02-24 17:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24 16:25 [PATCH v5 0/4] List supported formats in libv4l2subdev Sakari Ailus
2016-02-24 16:25 ` Sakari Ailus [this message]
2016-02-24 16:25 ` [PATCH v5 2/4] libv4l2subdev: Use generated format definitions " Sakari Ailus
2016-02-24 16:25 ` [PATCH v5 3/4] libv4l2subdev: Add a function to list library supported pixel codes Sakari Ailus
2016-02-25 21:30   ` Laurent Pinchart
2016-02-24 16:25 ` [PATCH v5 4/4] media-ctl: List supported media bus formats Sakari Ailus
2016-02-25 21:38   ` Laurent Pinchart
2016-02-25 21:48     ` Sakari Ailus
2016-02-25 21:52     ` Sakari Ailus
2016-02-25 21:52       ` [v4l-utils PATCH v5.1 " 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=1456331128-7036-2-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 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.