From: Julia Lawall <Julia.Lawall@lip6.fr> To: Mauro Carvalho Chehab <mchehab@kernel.org> Cc: kernel-janitors@vger.kernel.org, linux-media@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH 0/2] constify structures stored in fields of v4l2_subdev_ops structure Date: Sat, 27 Oct 2018 14:49:03 +0200 [thread overview] Message-ID: <1540644545-26184-1-git-send-email-Julia.Lawall@lip6.fr> (raw) The fields of a v4l2_subdev_ops structure are all const, so the structures that are stored there and are not used elsewhere can be const as well. Done with the help of Coccinelle. --- drivers/media/i2c/ov7740.c | 4 ++-- drivers/media/platform/vimc/vimc-sensor.c | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Julia Lawall <Julia.Lawall@lip6.fr> To: Mauro Carvalho Chehab <mchehab@kernel.org> Cc: kernel-janitors@vger.kernel.org, linux-media@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH 0/2] constify structures stored in fields of v4l2_subdev_ops structure Date: Sat, 27 Oct 2018 12:49:03 +0000 [thread overview] Message-ID: <1540644545-26184-1-git-send-email-Julia.Lawall@lip6.fr> (raw) The fields of a v4l2_subdev_ops structure are all const, so the structures that are stored there and are not used elsewhere can be const as well. Done with the help of Coccinelle. --- drivers/media/i2c/ov7740.c | 4 ++-- drivers/media/platform/vimc/vimc-sensor.c | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-)
next reply other threads:[~2018-10-27 13:24 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-10-27 12:49 Julia Lawall [this message] 2018-10-27 12:49 ` [PATCH 0/2] constify structures stored in fields of v4l2_subdev_ops structure Julia Lawall 2018-10-27 12:49 ` [PATCH 1/2] media: ov7740: " Julia Lawall 2018-10-27 12:49 ` Julia Lawall 2018-10-27 12:49 ` [PATCH 2/2] media: vimc: " Julia Lawall 2018-10-27 12:49 ` Julia Lawall 2018-11-01 11:49 ` Helen Koike 2018-11-01 11:49 ` Helen Koike
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=1540644545-26184-1-git-send-email-Julia.Lawall@lip6.fr \ --to=julia.lawall@lip6.fr \ --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: linkBe 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.