linux-kernel - Re: [PATCH 1/2] clk: Fix error handling in fixed clock hardware type register fn

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 20 Mar 2012 23:33:05 -0700 (PDT)
From:	"Saravana Kannan" <skannan@...eaurora.org>
To:	"Turquette, Mike" <mturquette@...com>
Cc:	"Saravana Kannan" <skannan@...eaurora.org>,
	"Sascha Hauer" <s.hauer@...gutronix.de>,
	"Andrew Lunn" <andrew@...n.ch>,
	"Grant Likely" <grant.likely@...retlab.ca>,
	"Jamie Iles" <jamie@...ieiles.com>,
	"Jeremy Kerr" <jeremy.kerr@...onical.com>,
	"Magnus Damm" <magnus.damm@...il.com>,
	"Deepak Saxena" <dsaxena@...aro.org>,
	linux-arm-kernel@...ts.infradead.org,
	"Arnd Bergman" <arnd.bergmann@...aro.org>,
	linux-arm-msm@...r.kernel.org,
	"Rob Herring" <rob.herring@...xeda.com>,
	"Russell King" <linux@....linux.org.uk>,
	"Thomas Gleixner" <tglx@...utronix.de>,
	"Richard Zhao" <richard.zhao@...aro.org>,
	"Shawn Guo" <shawn.guo@...escale.com>,
	"Paul Walmsley" <paul@...an.com>,
	"Linus Walleij" <linus.walleij@...ricsson.com>,
	"Mark Brown" <broonie@...nsource.wolfsonmicro.com>,
	"Stephen Boyd" <sboyd@...eaurora.org>,
	linux-kernel@...r.kernel.org,
	"Amit Kucheria" <amit.kucheria@...aro.org>
Subject: Re: [PATCH 1/2] clk: Fix error handling in fixed clock hardware 
     type register fn


On Tue, March 20, 2012 10:45 pm, Turquette, Mike wrote:
> IIRC, that discussion was with respect to the .parent member of struct
> clk.  It was decided that having .parent = NULL does not imply that a
> clock is a root clock, but instead we rely on the CLK_IS_ROOT flag.  I
> can't think of any other instance where a NULL clk when returned from
> a registration function would be useful.

I wasn't referring to a discussion with regards to this patch series. I'm
referring to what I believe was a discussion with Russell King on whether
a NULL from clk_get() should be considered a clock and whether it should
be usable as a "clock" with the clock APIs. That's the reason clk_get()
returns -ENOENT instead of NULL.

-Saravana

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.


--
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/