linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
	Russell King - ARM Linux <linux@armlinux.org.uk>,
	Kees Cook <keescook@chromium.org>,
	andrew@lunn.ch, Jason Cooper <jason@lakedaemon.net>,
	rtc-linux@googlegroups.com, a.zummo@towertech.it,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	gregory.clement@free-electrons.com,
	Bhumika Goyal <bhumirks@gmail.com>,
	sebastian.hesselbarth@gmail.com
Subject: Re: [PATCH] rtc: armada38x: add __ro_after_init to armada38x_rtc_ops
Date: Wed, 4 Jan 2017 12:43:32 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1701041242080.3073@hadrien> (raw)
In-Reply-To: <20170104110750.dtu54t74qkuuvkvq@piout.net>

> The question was whether the point to the rtc_class_ops could be made
> __ro_after_init. And Russell is right, it is pointed to by the ops
> pointer in a struct rtc_device and that struct is dynamically allocated
> in rtc_device_register().

OK, I think it's a terminology issue.  You mean the structure that
contains the pointer, and not the pointer itself, which is already const.

thanks,
julia

  reply	other threads:[~2017-01-04 11:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-26 11:31 [PATCH] rtc: armada38x: add __ro_after_init to armada38x_rtc_ops Bhumika Goyal
2017-01-02 14:06 ` Russell King - ARM Linux
2017-01-03 21:18   ` Kees Cook
2017-01-03 21:31     ` Russell King - ARM Linux
2017-01-03 21:54       ` Russell King - ARM Linux
2017-01-04 10:57         ` Julia Lawall
2017-01-04 11:07           ` Alexandre Belloni
2017-01-04 11:43             ` Julia Lawall [this message]
2017-01-04 12:14               ` Russell King - ARM Linux
2017-01-04 12:23                 ` Julia Lawall
2017-01-04 13:06                   ` Russell King - ARM Linux
2017-01-04 13:41                     ` Julia Lawall
2017-01-04 21:53                     ` Kees Cook

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.DEB.2.20.1701041242080.3073@hadrien \
    --to=julia.lawall@lip6.fr \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=andrew@lunn.ch \
    --cc=bhumirks@gmail.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=jason@lakedaemon.net \
    --cc=keescook@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=rtc-linux@googlegroups.com \
    --cc=sebastian.hesselbarth@gmail.com \
    /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).