From: Dave Jones <davej@redhat.com>
To: cpufreq@vger.kernel.org
Subject: Re: cpufreq.next status
Date: Wed, 29 Feb 2012 23:32:24 -0500 [thread overview]
Message-ID: <20120301043223.GA11483@redhat.com> (raw)
In-Reply-To: <20120229195732.GB11311@redhat.com>
On Wed, Feb 29, 2012 at 02:57:33PM -0500, Dave Jones wrote:
> I just went through my backlog, and applied and pushed out what I had
> queued up. Half of the patches didn't apply.
> So if your patch isn't in what's on cpufreq.next on kernel.org right now,
> it needs rebasing and resending.
>
> Here are the ones that applied:
> Applying: [CPUFREQ] s3c64xx: Fix mis-cherry pick of VDDINT
> Applying: [CPUFREQ] EXYNOS: Initialize locking_frequency with initial frequency
> Applying: [CPUFREQ] EXYNOS4210: update the name of EXYNOS clock register
> Applying: [CPUFREQ] Fix exposure of ARM_EXYNOS4210_CPUFREQ
> Applying: [CPUFREQ] Add S3C2416/S3C2450 cpufreq driver
> Applying: [CPUFREQ] CPUfreq ondemand: update sampling rate without waiting for next sampling
> Applying: [CPUFREQ] ondemand: handle QoS request on DVFS response latency
I scrapped that tree, and just pushed out a recreated tree without the last two patches
(which without the dependant QoS patch that didn't apply, caused a build failure).
If you cloned/pulled this afternoon, you'll need to reclone without those bad commits.
Dave
prev parent reply other threads:[~2012-03-01 4:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 19:57 cpufreq.next status Dave Jones
2012-03-01 4:32 ` Dave Jones [this message]
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=20120301043223.GA11483@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@vger.kernel.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 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.