linux-kernel - Re: [PATCH 13/13] clk: basic: improve parent

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] [day] [month] [year] [list]

Message-ID: <293d03fc4c269b5359c0826b982cc4be.squirrel@www.codeaurora.org>
Date:	Wed, 25 Apr 2012 23:00:26 -0700 (PDT)
From:	"Saravana Kannan" <skannan@...eaurora.org>
To:	"Shawn Guo" <shawn.guo@...aro.org>
Cc:	linux-kernel@...r.kernel.org,
	"Saravana Kannan" <skannan@...eaurora.org>,
	"Andrew Lunn" <andrew@...n.ch>,
	"Mark Brown" <broonie@...nsource.wolfsonmicro.com>,
	"Russell King" <linux@....linux.org.uk>, patches@...aro.org,
	"Sascha Hauer" <s.hauer@...gutronix.de>,
	"Rajendra Nayak" <rnayak@...com>,
	"Olof Johansson" <olof@...om.net>, linaro-dev@...ts.linaro.org,
	arnd.bergmann@...aro.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 13/13] clk: basic: improve parent_names & return errors


On Tue, April 17, 2012 12:17 am, Shawn Guo wrote:
> On 17 April 2012 11:50, Turquette, Mike <mturquette@...com> wrote:
>> That is a good question.  I think it is worth waiting on Saravana's
>> patch which exposes non-private members of struct clk via struct
>> clk_hw.  This will have an effect on both platform clock data and
>> code.
>
> Saravana,
>
> (*nudge*) (*nudge*) goes to you now :)
>

Done! I especially like how it turned out.

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