From: Thomas Renninger <mail@renninger.de>
To: Dave Jones <davej@redhat.com>
Cc: linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org
Subject: Re: + cpufreq-_ppc-frequency-change-issues-freq-already-lowered-by-bios.patch added to -mm tree
Date: Wed, 01 Feb 2006 13:11:08 +0100 [thread overview]
Message-ID: <43E0A55C.6020700@renninger.de> (raw)
In-Reply-To: <20060131223115.GF29937@redhat.com>
Dave Jones wrote:
> On Tue, Jan 31, 2006 at 01:14:32PM -0800, Andrew Morton wrote:
> >
> > The patch titled
> >
> > cpufreq: _PPC frequency change issues - freq already lowered by BIOS
> >
> > has been added to the -mm tree. Its filename is
> >
> > cpufreq-_ppc-frequency-change-issues-freq-already-lowered-by-bios.patch
> >
> > See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
> > out what to do about this
> >
>
> *puzzled look*
>
> I merged this into cpufreq-git last week.
>
> diff-tree 0961dd0... (from c70ca00...)
> Author: Thomas Renninger <trenn@suse.de>
> Date: Thu Jan 26 18:46:33 2006 +0100
>
> [CPUFREQ] _PPC frequency change issues
>
>
>
> Did your pull fail for some reason?
>
> Dave
I got this answer from Andrew, maybe he also picked up the patch
from cpufreq list?:
____________
This generates 100% rejects against the current cpufreq tree. I'd suggest
that you prepare patches against latest -mm, which includes
git-cpufreq.patch.
Please also include the required Signed-off-by: tags, as per section 11 of
Documentation/SubmittingPatches.
____________
The patch needs a (!policy->cur) check for some cpufreq drivers, shall I resend
the whole patch with this one added or is the "ontop" patch I answered to
avuton@gmail.com (Subject: Re: [PATCH 2/2] Re: 2.6.16-rc1-mm4) enough?
Thomas
next prev parent reply other threads:[~2006-02-01 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200601312112.k0VLCRdV031988@shell0.pdx.osdl.net>
2006-01-31 22:31 ` + cpufreq-_ppc-frequency-change-issues-freq-already-lowered-by-bios.patch added to -mm tree Dave Jones
2006-02-01 12:11 ` Thomas Renninger [this message]
2006-02-01 16:18 ` 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=43E0A55C.6020700@renninger.de \
--to=mail@renninger.de \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox