From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751374AbdADLpG (ORCPT ); Wed, 4 Jan 2017 06:45:06 -0500 Received: from mail3-relais-sop.national.inria.fr ([192.134.164.104]:1926 "EHLO mail3-relais-sop.national.inria.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751190AbdADLpE (ORCPT ); Wed, 4 Jan 2017 06:45:04 -0500 X-IronPort-AV: E=Sophos;i="5.33,459,1477954800"; d="scan'208";a="206917980" Date: Wed, 4 Jan 2017 12:43:32 +0100 (CET) From: Julia Lawall X-X-Sender: jll@hadrien To: Alexandre Belloni cc: Julia Lawall , Russell King - ARM Linux , Kees Cook , andrew@lunn.ch, Jason Cooper , rtc-linux@googlegroups.com, a.zummo@towertech.it, LKML , "linux-arm-kernel@lists.infradead.org" , gregory.clement@free-electrons.com, Bhumika Goyal , sebastian.hesselbarth@gmail.com Subject: Re: [PATCH] rtc: armada38x: add __ro_after_init to armada38x_rtc_ops In-Reply-To: <20170104110750.dtu54t74qkuuvkvq@piout.net> Message-ID: References: <1482751862-18699-1-git-send-email-bhumirks@gmail.com> <20170102140654.GF14217@n2100.armlinux.org.uk> <20170103213118.GM14217@n2100.armlinux.org.uk> <20170103215421.GN14217@n2100.armlinux.org.uk> <20170104110750.dtu54t74qkuuvkvq@piout.net> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Sender: rtc-linux@googlegroups.com Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr. [192.134.164.104]) by gmr-mx.google.com with ESMTPS id 75si2687158wme.3.2017.01.04.03.43.37 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Jan 2017 03:43:37 -0800 (PST) Date: Wed, 4 Jan 2017 12:43:32 +0100 (CET) From: Julia Lawall To: Alexandre Belloni cc: Julia Lawall , Russell King - ARM Linux , Kees Cook , andrew@lunn.ch, Jason Cooper , rtc-linux@googlegroups.com, a.zummo@towertech.it, LKML , "linux-arm-kernel@lists.infradead.org" , gregory.clement@free-electrons.com, Bhumika Goyal , sebastian.hesselbarth@gmail.com Subject: [rtc-linux] Re: [PATCH] rtc: armada38x: add __ro_after_init to armada38x_rtc_ops In-Reply-To: <20170104110750.dtu54t74qkuuvkvq@piout.net> Message-ID: References: <1482751862-18699-1-git-send-email-bhumirks@gmail.com> <20170102140654.GF14217@n2100.armlinux.org.uk> <20170103213118.GM14217@n2100.armlinux.org.uk> <20170103215421.GN14217@n2100.armlinux.org.uk> <20170104110750.dtu54t74qkuuvkvq@piout.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Reply-To: rtc-linux@googlegroups.com List-ID: List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , > 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 -- You received this message because you are subscribed to "rtc-linux". Membership options at http://groups.google.com/group/rtc-linux . Please read http://groups.google.com/group/rtc-linux/web/checklist before submitting a driver. --- You received this message because you are subscribed to the Google Groups "rtc-linux" group. To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/d/optout. From mboxrd@z Thu Jan 1 00:00:00 1970 From: julia.lawall@lip6.fr (Julia Lawall) Date: Wed, 4 Jan 2017 12:43:32 +0100 (CET) Subject: [PATCH] rtc: armada38x: add __ro_after_init to armada38x_rtc_ops In-Reply-To: <20170104110750.dtu54t74qkuuvkvq@piout.net> References: <1482751862-18699-1-git-send-email-bhumirks@gmail.com> <20170102140654.GF14217@n2100.armlinux.org.uk> <20170103213118.GM14217@n2100.armlinux.org.uk> <20170103215421.GN14217@n2100.armlinux.org.uk> <20170104110750.dtu54t74qkuuvkvq@piout.net> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org > 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