From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kukjin Kim Subject: Re: Fix exposure of ARM_EXYNOS4210_CPUFREQ Date: Wed, 04 Apr 2012 09:43:28 -0700 Message-ID: <4F7C7A30.6000406@samsung.com> References: <20120213094940.GA15338@n2100.arm.linux.org.uk> <4F3CF3DA.7000806@samsung.com> <20120216160250.GP13673@n2100.arm.linux.org.uk> <00aa01ccf084$93c98a70$bb5c9f50$%kim@samsung.com> <20120327074931.GK5611@n2100.arm.linux.org.uk> <4F73B3E1.4080807@samsung.com> <20120404145204.GA24211@n2100.arm.linux.org.uk> <20120404145917.GB1929@redhat.com> <20120404150353.GB24211@n2100.arm.linux.org.uk> <20120404150730.GC24211@n2100.arm.linux.org.uk> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=7HYF46Kqz2cPHFjB9v8tGf3oYAM3X16wIMTSLKIpjho=; b=sMvY3FWJmXeIye4rC2fDQGyKEdRdQRFCIxbK+wxgCU9yZvcNyMK1F4XhGOdSPXZAHr d69yDt0gl6maeO8y7hPOlL8XSV4kiJ9g051oJvWZ+mpvtlcBnpP6e81/CBWOB2f0VOxc EuOumAExV7Kgxqt0TJ3OCmUouGTTCx8496YXXXmOehdJcmnCPeO81R9x84BNMRO1Nxx+ AHmEC2Hb43sdxIquKQU9ZbQQz628/qjdAzlPGy4Ew1z5hnt3P5KEdyT8l7fw0c/1znb7 g3CiQPxVwinZ/Cco5m2FCo6GUv8Vx/hmB7AZPtXsEm5S7R9YtegSV8DnMICoCBOzGrIO cQNg== In-Reply-To: <20120404150730.GC24211@n2100.arm.linux.org.uk> Sender: cpufreq-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Russell King - ARM Linux Cc: 'Dave Jones' , Kukjin Kim , cpufreq@vger.kernel.org, linux-arm-kernel@lists.infradead.org On 04/04/12 08:07, Russell King - ARM Linux wrote: > On Wed, Apr 04, 2012 at 04:03:53PM +0100, Russell King - ARM Linux wrote: >> On Wed, Apr 04, 2012 at 10:59:17AM -0400, 'Dave Jones' wrote: >>> On Wed, Apr 04, 2012 at 03:52:04PM +0100, Russell King - ARM Linux wrote: >>> > On Wed, Mar 28, 2012 at 05:59:13PM -0700, Kukjin Kim wrote: >>> > > Russell King wrote: >>> > >> As predicted, this is breaking other ARM platforms. Please fix this >>> > >> yourself before your crappy code gets pushed into mainline. Thanks. >>> > >> >>> > > I fixed it. >>> > >>> > When will we see patches or the fix in mainline? >>> >>> Just send it to Linus directly. >> >> 'it'... well, that implies that someone already has a patch. I've asked >> Kukjin to fix the problem which he introduced because exynos is getting >> rather complicated, and he'll know what the dependencies should be. So >> far I've yet to see any kind of patch fixing this stuff. >> >> Meanwhile I'm seeing failing randconfig builds for non-exynos ARM for >> about a week due to the lack of dependencies. > > Actually, given that this has been known about since Feb 13th, I'm now > going to ask for the exynos cpufreq updates to be reverted because > there's clearly no motivation to fix this crap Kconfig shite. Having > it tossed out of mainline will provide the necessary motivation to get > people to fix their own fuckups. > Hmm, sorry about that. Actaully, I missed its fix when implemented cpufreq exynos4x12 and exynos5250. But as I said, its build failure has been introduced from last merge window, so I think, it can be fixed in this during -rc. Thanks. Best regards, Kgene. -- Kukjin Kim , Senior Engineer, SW Solution Development Team, Samsung Electronics Co., Ltd. From mboxrd@z Thu Jan 1 00:00:00 1970 From: kgene.kim@samsung.com (Kukjin Kim) Date: Wed, 04 Apr 2012 09:43:28 -0700 Subject: [CPUFREQ] Fix exposure of ARM_EXYNOS4210_CPUFREQ In-Reply-To: <20120404150730.GC24211@n2100.arm.linux.org.uk> References: <20120213094940.GA15338@n2100.arm.linux.org.uk> <4F3CF3DA.7000806@samsung.com> <20120216160250.GP13673@n2100.arm.linux.org.uk> <00aa01ccf084$93c98a70$bb5c9f50$%kim@samsung.com> <20120327074931.GK5611@n2100.arm.linux.org.uk> <4F73B3E1.4080807@samsung.com> <20120404145204.GA24211@n2100.arm.linux.org.uk> <20120404145917.GB1929@redhat.com> <20120404150353.GB24211@n2100.arm.linux.org.uk> <20120404150730.GC24211@n2100.arm.linux.org.uk> Message-ID: <4F7C7A30.6000406@samsung.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 04/04/12 08:07, Russell King - ARM Linux wrote: > On Wed, Apr 04, 2012 at 04:03:53PM +0100, Russell King - ARM Linux wrote: >> On Wed, Apr 04, 2012 at 10:59:17AM -0400, 'Dave Jones' wrote: >>> On Wed, Apr 04, 2012 at 03:52:04PM +0100, Russell King - ARM Linux wrote: >>> > On Wed, Mar 28, 2012 at 05:59:13PM -0700, Kukjin Kim wrote: >>> > > Russell King wrote: >>> > >> As predicted, this is breaking other ARM platforms. Please fix this >>> > >> yourself before your crappy code gets pushed into mainline. Thanks. >>> > >> >>> > > I fixed it. >>> > >>> > When will we see patches or the fix in mainline? >>> >>> Just send it to Linus directly. >> >> 'it'... well, that implies that someone already has a patch. I've asked >> Kukjin to fix the problem which he introduced because exynos is getting >> rather complicated, and he'll know what the dependencies should be. So >> far I've yet to see any kind of patch fixing this stuff. >> >> Meanwhile I'm seeing failing randconfig builds for non-exynos ARM for >> about a week due to the lack of dependencies. > > Actually, given that this has been known about since Feb 13th, I'm now > going to ask for the exynos cpufreq updates to be reverted because > there's clearly no motivation to fix this crap Kconfig shite. Having > it tossed out of mainline will provide the necessary motivation to get > people to fix their own fuckups. > Hmm, sorry about that. Actaully, I missed its fix when implemented cpufreq exynos4x12 and exynos5250. But as I said, its build failure has been introduced from last merge window, so I think, it can be fixed in this during -rc. Thanks. Best regards, Kgene. -- Kukjin Kim , Senior Engineer, SW Solution Development Team, Samsung Electronics Co., Ltd.