From: Mikhail Ulyanov <mikhail.ulyanov@cogentembedded.com>
To: Julia Lawall <Julia.Lawall@lip6.fr>
Cc: bhumirks@gmail.com, kernel-janitors@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 04/12] [media] V4L2: platform: rcar_jpu: constify v4l2_m2m_ops structures
Date: Thu, 10 Aug 2017 16:38:49 +0300 [thread overview]
Message-ID: <CALi4nhp_xQodYy9Y=Cma4NSJh5wwPKhSksfj+HAtJ4jnCMHrxg@mail.gmail.com> (raw)
In-Reply-To: <1502007921-22968-5-git-send-email-Julia.Lawall@lip6.fr>
On Sun, Aug 6, 2017 at 11:25 AM, Julia Lawall <Julia.Lawall@lip6.fr> wrote:
> The v4l2_m2m_ops structures are only passed as the only
> argument to v4l2_m2m_init, which is declared as const.
> Thus the v4l2_m2m_ops structures themselves can be const.
>
> Done with the help of Coccinelle.
>
> // <smpl>
> @r disable optional_qualifier@
> identifier i;
> position p;
> @@
> static struct v4l2_m2m_ops i@p = { ... };
>
> @ok1@
> identifier r.i;
> position p;
> @@
> v4l2_m2m_init(&i@p)
>
> @bad@
> position p != {r.p,ok1.p};
> identifier r.i;
> struct v4l2_m2m_ops e;
> @@
> e@i@p
>
> @depends on !bad disable optional_qualifier@
> identifier r.i;
> @@
> static
> +const
> struct v4l2_m2m_ops i = { ... };
> // </smpl>
>
> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
Acked-by: Ulyanov Mikhail <mikhail.ulyanov@cogentembedded.com>
next prev parent reply other threads:[~2017-08-10 13:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-06 8:25 [PATCH 00/12] constify v4l2_m2m_ops structures Julia Lawall
2017-08-06 8:25 ` [PATCH 01/12] [media] st-delta: " Julia Lawall
2017-08-06 8:25 ` [PATCH 02/12] [media] media: ti-vpe: vpe: " Julia Lawall
2017-08-06 8:25 ` [PATCH 03/12] [media] s5p-g2d: " Julia Lawall
[not found] ` <CGME20170807102341epcas2p2da8478bd73ca0678071912323830e456@epcas2p2.samsung.com>
2017-08-07 10:23 ` Sylwester Nawrocki
2017-08-06 8:25 ` [PATCH 04/12] [media] V4L2: platform: rcar_jpu: " Julia Lawall
2017-08-10 13:38 ` Mikhail Ulyanov [this message]
2017-08-06 8:25 ` [PATCH 05/12] [media] vcodec: mediatek: " Julia Lawall
2017-08-07 2:42 ` Rick Chang
2017-08-06 8:25 ` [PATCH 06/12] [media] exynos-gsc: " Julia Lawall
[not found] ` <CGME20170807101839epcas2p41e7c3092b876487e132a8a640e9ed262@epcas2p4.samsung.com>
2017-08-07 10:18 ` Sylwester Nawrocki
2017-08-06 8:25 ` [PATCH 07/12] [media] bdisp: " Julia Lawall
2017-08-06 8:25 ` [PATCH 08/12] [media] m2m-deinterlace: " Julia Lawall
2017-08-06 8:25 ` [PATCH 09/12] [media] media: mx2-emmaprp: " Julia Lawall
2017-08-06 8:25 ` [PATCH 10/12] [media] vim2m: " Julia Lawall
2017-08-06 8:25 ` [PATCH 11/12] [media] exynos4-is: " Julia Lawall
[not found] ` <CGME20170807101941epcas2p446c04b9a0813cb56f33202e6b4fdc49b@epcas2p4.samsung.com>
2017-08-07 10:19 ` Sylwester Nawrocki
2017-08-06 8:25 ` [PATCH 12/12] [media] mtk-mdp: " Julia Lawall
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='CALi4nhp_xQodYy9Y=Cma4NSJh5wwPKhSksfj+HAtJ4jnCMHrxg@mail.gmail.com' \
--to=mikhail.ulyanov@cogentembedded.com \
--cc=Julia.Lawall@lip6.fr \
--cc=bhumirks@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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).