All of lore.kernel.org
 help / color / mirror / Atom feed
From: walt <w41ter@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.37-ck1
Date: Sat, 15 Jan 2011 16:03:14 -0800	[thread overview]
Message-ID: <4D3235C2.7020104@gmail.com> (raw)
In-Reply-To: <201101061619.06992.kernel@kolivas.org>

On 01/05/2011 09:19 PM, Con Kolivas wrote:
> These are patches designed to improve system responsiveness and interactivity
> with specific emphasis on the desktop, but suitable to any workload.
>
>
> Apply to 2.6.37:
> http://www.kernel.org/pub/linux/kernel/people/ck/patches/2.6/2.6.37/2.6.37-
> ck1/patch-2.6.37-ck1.bz2

Thanks Con.  I can't build a ck kernel without CONFIG_HOTPLUG_CPU but I don't
know if this is a bug or a feature :)

Your latest sched_bfs.c encloses the subroutine sched_set_stop_task() inside of
an #ifdef CONFIG_HOTPLUG_CPU section.

But the most recent stop_machine.c uses that subroutine twice -- once inside of
an #ifdef CONFIG_HOTPLUG_CPU section, and again outside of that section.

The result is that stop_machine.o still needs sched_set_stop_task() even if
CONFIG_HOTPLUG_CPU is not defined, so the build fails in the link stage with
a missing symbol error.

Thanks for any suggestions/clarifications.


      reply	other threads:[~2011-01-16  0:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-06  5:19 2.6.37-ck1 Con Kolivas
2011-01-16  0:03 ` walt [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=4D3235C2.7020104@gmail.com \
    --to=w41ter@gmail.com \
    --cc=linux-kernel@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.