[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120409090920.GA28029@shlinux2.ap.freescale.net>
Date: Mon, 9 Apr 2012 17:09:22 +0800
From: Dong Aisheng <aisheng.dong@...escale.com>
To: Viresh Kumar <viresh.kumar@...com>
CC: Stephen Warren <swarren@...dotorg.org>,
Dong Aisheng-B29396 <B29396@...escale.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Linus WALLEIJ <linus.walleij@...ricsson.com>
Subject: Re: [PATCH 1/1] pinctrl: fix pinmux_check_ops error checking
On Mon, Apr 09, 2012 at 11:31:03AM +0800, Viresh Kumar wrote:
> On 4/6/2012 9:02 PM, Stephen Warren wrote:
> > On 04/06/2012 06:18 AM, Dong Aisheng wrote:
> >> > From: Dong Aisheng <dong.aisheng@...aro.org>
> >> >
> >> > Do not use get_functions_count before checking.
> >> >
> >> > Signed-off-by: Dong Aisheng <dong.aisheng@...aro.org>
> > Acked-by: Stephen Warren <swarren@...dotorg.org>
> >
> > IIRC, Viresh added some other get_*_count() functions in the same patch.
> > Do we need any more fixes similar to the this for those too?
>
> Might not be required as this patch handles the pinmux_check_ops() routine.
> At other places ops is guaranteed to have correct value.
>
Yes, core can guarantee it after pinmux_check_ops.
But i noticed for user interfaces, we may still need add some error checking
to avoid kernel oops like pinctrl_get_* and debugfs interfaces in case
the mux or config function is not supported by driver.
I'm going to send one more patch to fix it.
Regards
Dong Aisheng
--
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