All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kukjin Kim <kgene.kim@samsung.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: 'Dave Jones' <davej@redhat.com>,
	Kukjin Kim <kgene.kim@samsung.com>,
	linux-arm-kernel@lists.infradead.org, cpufreq@vger.kernel.org
Subject: Re: Fix exposure of ARM_EXYNOS4210_CPUFREQ
Date: Wed, 04 Apr 2012 09:39:30 -0700	[thread overview]
Message-ID: <4F7C7942.2000006@samsung.com> (raw)
In-Reply-To: <20120404150353.GB24211@n2100.arm.linux.org.uk>

On 04/04/12 08:03, 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.
>
Well, I already submitted its fix and it was including your e-mail. See 
below.

http://www.spinics.net/lists/cpufreq/msg03080.html

> Meanwhile I'm seeing failing randconfig builds for non-exynos ARM for
> about a week due to the lack of dependencies.
>

Yeah, the failure from cpufreq exynos4x12 and exynos5250 has been 
introduced from last merge window and you know exynos4210 has been fixed 
by your patch last time.

Thanks.

Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.

WARNING: multiple messages have this Message-ID (diff)
From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [CPUFREQ] Fix exposure of ARM_EXYNOS4210_CPUFREQ
Date: Wed, 04 Apr 2012 09:39:30 -0700	[thread overview]
Message-ID: <4F7C7942.2000006@samsung.com> (raw)
In-Reply-To: <20120404150353.GB24211@n2100.arm.linux.org.uk>

On 04/04/12 08:03, 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.
>
Well, I already submitted its fix and it was including your e-mail. See 
below.

http://www.spinics.net/lists/cpufreq/msg03080.html

> Meanwhile I'm seeing failing randconfig builds for non-exynos ARM for
> about a week due to the lack of dependencies.
>

Yeah, the failure from cpufreq exynos4x12 and exynos5250 has been 
introduced from last merge window and you know exynos4210 has been fixed 
by your patch last time.

Thanks.

Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.

  parent reply	other threads:[~2012-04-04 16:39 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13  9:49 Fix exposure of ARM_EXYNOS4210_CPUFREQ Russell King - ARM Linux
2012-02-13  9:49 ` [CPUFREQ] " Russell King - ARM Linux
2012-02-16 12:17 ` Kukjin Kim
2012-02-16 12:17   ` [CPUFREQ] " Kukjin Kim
2012-02-16 16:02   ` Russell King - ARM Linux
2012-02-16 16:02     ` [CPUFREQ] " Russell King - ARM Linux
2012-02-21 10:35     ` Kukjin Kim
2012-02-21 10:35       ` [CPUFREQ] " Kukjin Kim
2012-03-27  7:49       ` Russell King - ARM Linux
2012-03-27  7:49         ` [CPUFREQ] " Russell King - ARM Linux
2012-03-29  0:59         ` Kukjin Kim
2012-03-29  0:59           ` [CPUFREQ] " Kukjin Kim
2012-04-04 14:52           ` Russell King - ARM Linux
2012-04-04 14:52             ` [CPUFREQ] " Russell King - ARM Linux
2012-04-04 14:59             ` 'Dave Jones'
2012-04-04 14:59               ` [CPUFREQ] " 'Dave Jones'
2012-04-04 15:03               ` Russell King - ARM Linux
2012-04-04 15:03                 ` [CPUFREQ] " Russell King - ARM Linux
2012-04-04 15:07                 ` Russell King - ARM Linux
2012-04-04 15:07                   ` [CPUFREQ] " Russell King - ARM Linux
2012-04-04 15:13                   ` Russell King - ARM Linux
2012-04-04 15:13                     ` [CPUFREQ] " Russell King - ARM Linux
2012-04-04 16:48                     ` Kukjin Kim
2012-04-04 16:48                       ` [CPUFREQ] " Kukjin Kim
2012-04-04 16:43                   ` Kukjin Kim
2012-04-04 16:43                     ` [CPUFREQ] " Kukjin Kim
2012-04-04 16:39                 ` Kukjin Kim [this message]
2012-04-04 16:39                   ` Kukjin Kim
2012-04-04 17:05               ` Kukjin Kim
2012-04-04 17:05                 ` [CPUFREQ] " Kukjin Kim
2012-04-04 17:22                 ` 'Dave Jones'
2012-04-04 17:22                   ` [CPUFREQ] " 'Dave Jones'

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F7C7942.2000006@samsung.com \
    --to=kgene.kim@samsung.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=davej@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux@arm.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.