From: Mike Fedyk <mfedyk@matchmail.com>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Updated preempt-kernel patches
Date: Fri, 12 Oct 2001 17:27:02 -0700 [thread overview]
Message-ID: <20011012172702.A16500@mikef-linux.matchmail.com> (raw)
In-Reply-To: <1002917978.957.86.camel@phantasy> <1002925193.868.5.camel@phantasy>
In-Reply-To: <1002925193.868.5.camel@phantasy>
On Fri, Oct 12, 2001 at 06:19:52PM -0400, Robert Love wrote:
> On Fri, 2001-10-12 at 16:19, Robert Love wrote:
> > - fix compile on SMP in some configurations (ac tree only)
>
> Looks like I forgot to merge that one. Fix follows below (its needed by
> some ac-tree users who also compile SMP).
>
Again? ;)
Any idea how it would work on any smp systems using the -ac tree?
next prev parent reply other threads:[~2001-10-13 0:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-12 20:19 Updated preempt-kernel patches Robert Love
2001-10-12 20:47 ` Robert Love
2001-10-12 22:19 ` Robert Love
2001-10-13 0:27 ` Mike Fedyk [this message]
2001-10-13 0:32 ` Robert Love
2001-10-13 1:01 ` Mike Fedyk
2001-10-13 5:31 ` Robert Love
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=20011012172702.A16500@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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