From: Andrew Morton <akpm@linux-foundation.org>
To: Dave Jones <davej@redhat.com>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
Greg.Chandler@wellsfargo.com, cpufreq@lists.linux.org.uk,
linux-kernel@vger.kernel.org, dan.j.williams@intel.com,
Andi Kleen <ak@suse.de>
Subject: Re: [PATCH 1/1] Kernel compile bug in 2.6.22.6/7 {maybe more} ARM/StrongARM
Date: Tue, 25 Sep 2007 10:31:42 -0700 [thread overview]
Message-ID: <20070925103142.c93719b3.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070925172255.GL8127@redhat.com>
On Tue, 25 Sep 2007 13:22:55 -0400 Dave Jones <davej@redhat.com> wrote:
> >
> > OK, here: ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc5/2.6.21-rc5-mm3/broken-out/fix-x86_64-mm-sched-clock-share.patch
> >
> > So I guess what we want to do here is to revert that patch, test i386
> > allnoconfig and then fix up anything which breaks.
>
> Nothing breaks for me with make ARCH=i386 bzImage on my x86-64 box
> (which should be the same as a native build).
Was that with allnoconfig?
> The functions that complain in that patch header don't seem to actually
> exist in mainline at all. (`init_sched_clock' and `call_r_s_f')
> Did this patch perhaps jump the gun, and these are -mm only ?
Could be that this patch fixed version 17 of sched-clock-share and we ended
up merging verion 56. It was awful.
next prev parent reply other threads:[~2007-09-25 17:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1E7A4807A136DF45AD33DB341D93C3BD1F0C19@msgswbmnmsp46.wellsfargo.com>
2007-09-25 7:31 ` [PATCH 1/1] Kernel compile bug in 2.6.22.6/7 {maybe more} ARM/StrongARM Russell King
2007-09-25 14:36 ` Dave Jones
2007-09-25 16:52 ` Andrew Morton
2007-09-25 16:58 ` Dave Jones
2007-09-25 17:08 ` Andrew Morton
2007-09-25 17:22 ` Dave Jones
2007-09-25 17:31 ` Andrew Morton [this message]
2007-09-25 17:51 ` Dave Jones
2007-09-26 20:53 ` Dave Jones
2007-09-29 17:59 ` Russell King
2007-09-25 17:31 ` Greg.Chandler
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=20070925103142.c93719b3.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Greg.Chandler@wellsfargo.com \
--cc=ak@suse.de \
--cc=cpufreq@lists.linux.org.uk \
--cc=dan.j.williams@intel.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox