From: Dave Jones <davej@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
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 13:22:55 -0400 [thread overview]
Message-ID: <20070925172255.GL8127@redhat.com> (raw)
In-Reply-To: <20070925100839.8d2e7b40.akpm@linux-foundation.org>
On Tue, Sep 25, 2007 at 10:08:39AM -0700, Andrew Morton wrote:
> On Tue, 25 Sep 2007 12:58:34 -0400 Dave Jones <davej@redhat.com> wrote:
>
> > On Tue, Sep 25, 2007 at 09:52:29AM -0700, Andrew Morton wrote:
> > > On Tue, 25 Sep 2007 10:36:51 -0400 Dave Jones <davej@redhat.com> wrote:
> > > >
> > > > commit 184c44d2049c4db7ef6ec65794546954da2c6a0e
> > > > Author: Andrew Morton <akpm@linux-foundation.org>
> > > > Date: Wed May 2 19:27:08 2007 +0200
> > > >
> > > > [PATCH] x86-64: fix x86_64-mm-sched-clock-share
> > > >
> > > > Fix for the following patch. Provide dummy cpufreq functions when
> > > > CPUFREQ is not compiled in.
> > > >
> > > > Cc: Andi Kleen <ak@suse.de>
> > > > Cc: Dave Jones <davej@codemonkey.org.uk>
> > > > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> > > > Signed-off-by: Andi Kleen <ak@suse.de>
> > > >
> > > > I don't remember seeing any problem here, so I'm not entirely sure what
> > > > this was supposed to be fixing. Perhaps the -mm-esque patch name
> > > > will provide Andrew/Andi clues. It lacks sufficient information for
> > > > my brain to guess what the problem was.
> > >
> > > Oh geeze. sched-clock-share went through about 18 different versions, was
> > > merged, unmerged, remerged, dropped, etc. I don't recall at what stage in
> > > this mess the above fix was inserted, sorry.
> > >
> > > > "Fix for the following patch" is also something that really should
> > > > never be added to a git changelog too, because 'next' means absolutely
> > > > nothing to me, nor I expect 99% of changelog readers.
> > >
> > > 184c44d2049c4db7ef6ec65794546954da2c6a0e should never have existed,
> > > actually. I intended that Andi fold it into the base patch prior to
> > > sending it to Linus. He normally does that, but it looks like this
> > > one was handled as a standalone commit for some reason.
> >
> > So lets see what happens if we revert it ?
> >
>
> <grep flurry>
>
> 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).
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 ?
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-09-25 17:22 UTC|newest]
Thread overview: 20+ 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 14:36 ` Dave Jones
2007-09-25 16:52 ` Andrew Morton
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:08 ` Andrew Morton
2007-09-25 17:22 ` Dave Jones [this message]
2007-09-25 17:31 ` Andrew Morton
2007-09-25 17:31 ` Andrew Morton
2007-09-25 17:51 ` Dave Jones
2007-09-26 20:53 ` Dave Jones
2007-09-26 20:53 ` Dave Jones
2007-09-29 17:59 ` Russell King
2007-09-29 17:59 ` Russell King
2007-09-25 17:31 ` Greg.Chandler
2007-09-25 17:31 ` Greg.Chandler
2007-10-10 23:18 ` arm root filesystem Greg.Chandler
2007-10-11 0:30 ` 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=20070925172255.GL8127@redhat.com \
--to=davej@redhat.com \
--cc=Greg.Chandler@wellsfargo.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=cpufreq@lists.linux.org.uk \
--cc=dan.j.williams@intel.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 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.