linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [CPUFREQ] Fix exposure of ARM_EXYNOS4210_CPUFREQ
Date: Wed, 4 Apr 2012 16:13:46 +0100	[thread overview]
Message-ID: <20120404151346.GD24211@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20120404150730.GC24211@n2100.arm.linux.org.uk>

On Wed, Apr 04, 2012 at 04:07:30PM +0100, 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.

In case it's not clear - the problem applies to _all_ exynos stuff not
just the one which I had previously sent a patch for and you appear to
have applied.  Just look at the crap which was spat out today:

http://www.arm.linux.org.uk/developer/build/result.php?type=build&idx=546

  reply	other threads:[~2012-04-04 15:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13  9:49 [CPUFREQ] Fix exposure of ARM_EXYNOS4210_CPUFREQ Russell King - ARM Linux
2012-02-16 12:17 ` Kukjin Kim
2012-02-16 16:02   ` Russell King - ARM Linux
2012-02-21 10:35     ` Kukjin Kim
2012-03-27  7:49       ` Russell King - ARM Linux
2012-03-29  0:59         ` Kukjin Kim
2012-04-04 14:52           ` Russell King - ARM Linux
2012-04-04 14:59             ` 'Dave Jones'
2012-04-04 15:03               ` Russell King - ARM Linux
2012-04-04 15:07                 ` Russell King - ARM Linux
2012-04-04 15:13                   ` Russell King - ARM Linux [this message]
2012-04-04 16:48                     ` Kukjin Kim
2012-04-04 16:43                   ` Kukjin Kim
2012-04-04 16:39                 ` Kukjin Kim
2012-04-04 17:05               ` Kukjin Kim
2012-04-04 17:22                 ` '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=20120404151346.GD24211@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).