[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdY09qAog4soXf12w71vbk9EX3dvE_0Kuisw4iai9+rDXA@mail.gmail.com>
Date: Thu, 20 Oct 2011 11:54:08 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Barry Song <21cnbao@...il.com>
Cc: Stephen Warren <swarren@...dia.com>,
Linus Walleij <linus.walleij@...ricsson.com>,
linux-kernel@...r.kernel.org, Shawn Guo <shawn.guo@...escale.com>,
Sascha Hauer <s.hauer@...gutronix.de>,
David Brown <davidb@...eaurora.org>,
Grant Likely <grant.likely@...retlab.ca>,
Rongjun Ying <Rongjun.Ying@....com>,
Linaro Dev <linaro-dev@...ts.linaro.org>,
DL-SHA-WorkGroupLinux <workgroup.linux@....com>
Subject: Re: [PATCH 2/4] pinctrl: Remove unsafe __refdata
On Thu, Oct 20, 2011 at 11:46 AM, Barry Song <21cnbao@...il.com> wrote:
> 2011/10/20 Stephen Warren <swarren@...dia.com>:
>> A pin controller's pin definitions are used both during pinctrl_register()
>> and pinctrl_unregister(). The latter happens outside of __init/__devinit
>> time, and hence it is unsafe to mark the pin array as __refdata.
>
> Thanks.
> Acked-by: Barry Song <Baohua.Song@....com>
>
> missed this when porting prima2 pinmux driver. is this __refdata used
> just due to a typo?
No the problem was I misunderstood what __refdata means.
It means it is kept around but can reference initidata.
But I thought it meant "kept around in general".
I don't think it's causing bugs actually because it wasn't referencing
any initdata. But it's better like this.
Thanks,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists