[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1301021031490.1994@hadrien>
Date: Wed, 2 Jan 2013 10:44:32 +0100 (CET)
From: Julia Lawall <julia.lawall@...6.fr>
To: Russell King - ARM Linux <linux@....linux.org.uk>
cc: Dan Carpenter <error27@...il.com>,
Sylwester Nawrocki <sylvester.nawrocki@...il.com>,
Tomasz Stanislawski <t.stanislaws@...sung.com>,
Sergei Shtylyov <sshtylyov@...sta.com>,
kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org,
Kyungmin Park <kyungmin.park@...sung.com>,
linux-arm-kernel@...ts.infradead.org, linux-media@...r.kernel.org
Subject: Re: [PATCH RESEND 6/6] clk: s5p-g2d: Fix incorrect usage of
IS_ERR_OR_NULL
On Wed, 2 Jan 2013, Russell King - ARM Linux wrote:
> On Wed, Jan 02, 2013 at 08:10:36AM +0300, Dan Carpenter wrote:
> > clk_get() returns NULL if CONFIG_HAVE_CLK is disabled.
> >
> > I told Tony about this but everyone has been gone with end of year
> > holidays so it hasn't been addressed.
> >
> > Tony, please fix it so people don't apply these patches until
> > clk_get() is updated to not return NULL. It sucks to have to revert
> > patches.
>
> How about people stop using IS_ERR_OR_NULL for stuff which it shouldn't
> be used for?
Perhaps the cases where clk_get returns NULL could have a comment
indicating that NULL does not represent a failure?
In 3.7.1, it looks like it might have been possible for NULL to be
returned by clk_get in arch/mips/loongson1/common/clock.c, but that
definition seems to be gone in a recent linux-next. The remaining
definitions look OK.
julia
--
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