From: Robert Love <rml@tech9.net>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Andrea Arcangeli <andrea@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.20pre8aa2
Date: 02 Oct 2002 18:18:27 -0400 [thread overview]
Message-ID: <1033597107.27343.44.camel@phantasy> (raw)
In-Reply-To: <20021002214540.GA2589@werewolf.able.es>
On Wed, 2002-10-02 at 17:45, J.A. Magallon wrote:
> I was rediffing the task_cpu patch, when reached a new hunk in -aa:
>
> kernel/sched.c::sched_init(void):
>
> + current->cpu = smp_processor_id();
Ew we do that in 2.5, too.
I think this is a mistake; we don't need to do this here. But if I am
wrong, we need to get the current processor number elsewhere.
Robert Love
next prev parent reply other threads:[~2002-10-02 22:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 7:11 2.4.20pre8aa2 Andrea Arcangeli
2002-10-02 21:45 ` 2.4.20pre8aa2 J.A. Magallon
2002-10-02 22:12 ` 2.4.20pre8aa2 Andrea Arcangeli
2002-10-02 22:18 ` Robert Love [this message]
2002-10-02 23:30 ` 2.4.20pre8aa2 - i8k compile failure Eyal Lebedinsky
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=1033597107.27343.44.camel@phantasy \
--to=rml@tech9.net \
--cc=andrea@suse.de \
--cc=jamagallon@able.es \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).