mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Paul Jackson <pj@sgi.com>
Cc: rajesh.shah@intel.com, mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/1] export cpu_online_map
Date: Thu, 27 Oct 2005 02:35:48 -0700	[thread overview]
Message-ID: <20051027023548.0471db17.akpm@osdl.org> (raw)
In-Reply-To: <20051027015504.5a20ed05.pj@sgi.com>

Paul Jackson <pj@sgi.com> wrote:
>
> Andrew wrote:
> > > Since bk no longer works for me, I have no idea how to access any
> > > history prior to about 2.6.12-rc2.  Ugh.
> > 
> > There's still bkbits.net:
> > 
> > http://linux.bkbits.net:8080/linux-2.6/...
> 
> Ok - that helps.  Thanks.
> 
> There is also an hg (mercurial) web based Linux history at:
> 
>   http://www.kernel.org/hg/linux-2.6/
> 
> I still don't see something I can download into a local
> hg or git repository -- if a lurker knows how that is done,
> I'd be glad to know.
> 

I think there are ways of getting the entire kernel history in git too.

I usually just grep my patches directory, actually.  <looks>.  <egad>.
27,000 of them.

> 
> > Seems silly to use cpu_online_map to test for `1'?
> 
> Yeah - agreed.  The include/linux/cpumask.h stuff hardcodes
> the UP (NR_CPUS==1) code to plain old 0's and 1's.  This
> macro should do so as well.
> 
> I just sent a patch.
> 

Sweet, thanks.  Perhaps we can remove cpu_online_map from UP builds soon -
it's really wrong to have it there.

  reply	other threads:[~2005-10-27  9:36 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
2005-10-27  4:08   ` Andrew Morton
2005-10-27  8:55     ` Paul Jackson
2005-10-27  9:35       ` Andrew Morton [this message]
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=20051027023548.0471db17.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pj@sgi.com \
    --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

all inboxes | Powered by JetHome®