From: Dave Jones <davej@redhat.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
cpufreq@lists.linux.org.uk
Subject: Re: [discuss] 2.6.19-rc6: known regressions (v4)
Date: Tue, 21 Nov 2006 16:56:45 -0500 [thread overview]
Message-ID: <20061121215645.GD9651@redhat.com> (raw)
In-Reply-To: <20061121213900.GT5200@stusta.de>
On Tue, Nov 21, 2006 at 10:39:00PM +0100, Adrian Bunk wrote:
> On Tue, Nov 21, 2006 at 04:31:39PM -0500, Dave Jones wrote:
> > On Tue, Nov 21, 2006 at 10:24:24PM +0100, Adrian Bunk wrote:
> >
> > > Subject : CPU_FREQ_GOV_ONDEMAND=y compile error
> > > References : http://lkml.org/lkml/2006/11/17/198
> > > Submitter : alex1000@comcast.net
> > > Caused-By : Alexey Starikovskiy <alexey_y_starikovskiy@linux.intel.com>
> > > commit 05ca0350e8caa91a5ec9961c585c98005b6934ea
> > > Handled-By : Mattia Dongili <malattia@linux.it>
> > > Patch : http://lkml.org/lkml/2006/11/17/236
> > > Status : patch available
> >
> > not a regression, easily worked around, queued for .20
>
> It is a regression since commit 05ca0350e8caa91a5ec9961c585c98005b6934ea
> was merged after 2.6.18.
Ah, I misinterpreted when that cset went in (I read the commit date
which was back in June, not the merge date, which was september).
> Considering that the fix is trivial, why shouldn't it be merged before
> 2.6.19?
Yes, I'll push it on.
Dave
--
http://www.codemonkey.org.uk
prev parent reply other threads:[~2006-11-21 21:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0611152008450.3349@woody.osdl.org>
2006-11-17 20:40 ` 2.6.19-rc6: known regressions (v2) Adrian Bunk
2006-11-20 19:53 ` 2.6.19-rc6: known regressions (v3) Adrian Bunk
2006-11-21 21:24 ` 2.6.19-rc6: known regressions (v4) Adrian Bunk
2006-11-21 21:31 ` [discuss] " Dave Jones
2006-11-21 21:39 ` Adrian Bunk
2006-11-21 21:56 ` 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=20061121215645.GD9651@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=cpufreq@lists.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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