From: ulli.kroll@googlemail.com (Hans Ulli Kroll)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] rtc: constify rtc_class_ops structures
Date: Thu, 1 Sep 2016 12:21:26 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1609011219330.31401@T520> (raw)
In-Reply-To: <1472630725-25465-1-git-send-email-Julia.Lawall@lip6.fr>
Hi Julia
On Wed, 31 Aug 2016, Julia Lawall wrote:
> Check for rtc_class_ops structures that are only passed to
> devm_rtc_device_register, rtc_device_register,
> platform_device_register_data, all of which declare the corresponding
> parameter as const. Declare rtc_class_ops structures that have these
> properties as const.
>
> The semantic patch that makes this change is as follows:
> (http://coccinelle.lip6.fr/)
>
>
> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
for drivers/rtc/rtc-gemini.c
Acked-by: Hans Ulli Kroll <ulli.kroll@googlemail.com>
next prev parent reply other threads:[~2016-09-01 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 8:05 [PATCH] rtc: constify rtc_class_ops structures Julia Lawall
2016-08-31 17:43 ` Baruch Siach
2016-09-01 10:21 ` Hans Ulli Kroll [this message]
2016-09-01 10:32 ` Linus Walleij
2016-09-01 11:35 ` Thierry Reding
2016-09-02 20:32 ` Alexandre Belloni
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=alpine.LNX.2.00.1609011219330.31401@T520 \
--to=ulli.kroll@googlemail.com \
--cc=linux-arm-kernel@lists.infradead.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).