From: Paul Jackson <pj@sgi.com>
To: akpm@osdl.org
Cc: rajesh.shah@intel.com, mingo@elte.hu,
linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [patch 1/1] export cpu_online_map
Date: Wed, 26 Oct 2005 20:50:38 -0700 [thread overview]
Message-ID: <20051026205038.26a1c333.pj@sgi.com> (raw)
In-Reply-To: <200510260421.j9Q4LGh9014087@shell0.pdx.osdl.net>
Andrew asked:
> - Why isn't set_cpus_allowed() just a no-op on UP? Or some trivial thing
> which tests for cpu #0?
I don't know.
By scanning random copies of kernels left on my drive, I can see that
it changed from a trivial "return 0" to the more interesting check using
cpu_online_map in one of your "linus.patch" patches in the release
2.6.11-rc1-mm2.
But I don't know how to get to the history at this point to see what
happened.
It looks like Linus started the git history at 2.6.12-rc2.
Could someone clue me in on how to find Linux history BG (before-git)?
Since bk no longer works for me, I have no idea how to access any
history prior to about 2.6.12-rc2. Ugh.
--
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-27 3:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 4:20 akpm
2005-10-27 3:50 ` Paul Jackson [this message]
2005-10-27 4:08 ` Andrew Morton
2005-10-27 8:55 ` Paul Jackson
2005-10-27 9:35 ` Andrew Morton
2005-10-27 13:38 ` Paul Jackson
2005-10-27 18:26 ` Andrew Morton
2005-10-27 19:08 ` Paul Jackson
2005-10-27 13:49 ` Paul Jackson
2005-10-27 10:48 ` Diego Calleja
2005-10-27 14:06 ` Paul Jackson
2005-10-28 2:49 ` Herbert Xu
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=20051026205038.26a1c333.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rajesh.shah@intel.com \
/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
Powered by JetHome