From: Paul Jackson <pj@sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: magnus@valinux.co.jp, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CPUSETS: remove SMP dependency
Date: Wed, 26 Oct 2005 10:25:09 -0700 [thread overview]
Message-ID: <20051026102509.0b32006d.pj@sgi.com> (raw)
In-Reply-To: <20051026010922.5a8f70fe.akpm@osdl.org>
Andrew, responding to Magnus:
> > Remove the SMP dependency from CPUSETS.
>
> Why?
As described in the posting that Magnus linked to, it seemed to me
like the cleaner approach - if there is no need to link two CONFIG
options, then don't.
Perhaps someone wants to build a uni-processor (UP) kernel for other
reasons, but still have it support running some stuff that depends
on cpusets being present.
But my vote on UP issues isn't worth much. This patch is no biggie
to me either way.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2005-10-26 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 7:53 [PATCH] CPUSETS: remove SMP dependency Magnus Damm
2005-10-26 8:09 ` Andrew Morton
2005-10-26 8:19 ` Magnus Damm
2005-10-26 17:25 ` Paul Jackson [this message]
2005-10-27 3:25 ` Magnus Damm
-- strict thread matches above, loose matches on Subject: below --
2005-10-03 8:11 Magnus Damm
2005-10-03 8:43 ` Paul Jackson
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=20051026102509.0b32006d.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus@valinux.co.jp \
/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