[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5A40F824.5070100@gmail.com>
Date: Mon, 25 Dec 2017 18:37:48 +0530
From: arvindY <arvind.yadav.cs@...il.com>
To: Russell King - ARM Linux <linux@...linux.org.uk>
Cc: nsekhar@...com, khilman@...nel.org, kaloz@...nwrt.org,
khalasa@...p.pl, aaro.koskinen@....fi, tony@...mide.com,
jason@...edaemon.net, andrew@...n.ch,
sebastian.hesselbarth@...il.com,
gregory.clement@...e-electrons.com, daniel@...que.org,
haojian.zhuang@...il.com, robert.jarzmik@...e.fr,
marek.vasut@...il.com, slapin@...fans.org, jic23@....ac.uk,
kgene@...nel.org, krzk@...nel.org, ralf@...ux-mips.org,
ysato@...rs.sourceforge.jp, dalias@...c.org, tglx@...utronix.de,
mingo@...hat.com, hpa@...or.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/11] constify gpio_led
Hi Ressell,
On Saturday 23 December 2017 03:43 PM, Russell King - ARM Linux wrote:
> On Wed, Dec 20, 2017 at 02:17:41PM +0530, Arvind Yadav wrote:
>> gpio_led are not supposed to change at runtime.
>> struct gpio_led_platform_data working with const gpio_led
>> provided by <linux/leds.h>. So mark the non-const structs
>> as const.
> Marking the structs as const is fine, but marking them __initconst is
> not. The GPIO LED driver can be built as a module, which means it can
> be loaded after the init sections have gone away. If that happens,
> then we de-reference the pointer to memory that has been freed.
>
> Please re-spin your patch set without the __initconst marking.
>
Thanks for reviewing, As per your comment, I will send updated
patch. Which will not include __initconst.
~arvind
Powered by blists - more mailing lists