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]
Message-ID: <20150617190534.GB28251@katana>
Date:	Wed, 17 Jun 2015 21:05:35 +0200
From:	Wolfram Sang <wsa@...-dreams.de>
To:	York Sun <yorksun@...escale.com>
Cc:	mturquette@...libre.com, linux-kernel@...r.kernel.org,
	linux-i2c@...r.kernel.org, Paul Bolle <pebolle@...cali.nl>
Subject: Re: [RFC] drivers/clk/Kconfig: Change COMMON_CLK to tristate

On Wed, Jun 17, 2015 at 12:01:47PM -0700, York Sun wrote:
> COMMON_CLK has been a bool value, selected by the platforms who need
> common clock framework. If a CCF driver is needed on an add-on device
> such as PCIe card, COMMON_CLK can be selected individually as a
> tristate value.
> 
> Signed-off-by: York Sun <yorksun@...escale.com>
> CC: Paul Bolle <pebolle@...cali.nl>
> CC: Mike Turquette <mturquette@...libre.com>

Why do you CC the I2C list for clk patches??


Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ