From: Mike Fedyk <mfedyk@matchmail.com>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Compile Filure on 2.4.10-ac10+preempt+smp
Date: Tue, 9 Oct 2001 22:24:03 -0700 [thread overview]
Message-ID: <20011009222403.A12825@mikef-linux.matchmail.com> (raw)
In-Reply-To: <20011009214655.A26663@mikef-linux.matchmail.com> <1002690949.862.233.camel@phantasy>
In-Reply-To: <1002690949.862.233.camel@phantasy>
On Wed, Oct 10, 2001 at 01:15:25AM -0400, Robert Love wrote:
> On Wed, 2001-10-10 at 00:46, Mike Fedyk wrote:
> > Fail 2.4.10-ac10+preempt+smp
> > Success 2.4.10-ac10+preempt+up-apic+up-ipapic
> > Success 2.4.10-ac10+preempt
> > Success 2.4.10-ac10
> >
> > Robert, can you do a test compile for smp just in case?
>
> Ahh, yes. Thank you for spotting this. include/asm-i386/spinlock.h has
> two separate defines for spin_unlock and we only renamed one of them. I
> guess you hit the conditional that used the other define...
>
> The attached patch fixes it.
>
Thank you. Will compile now...
> > Also, I couldn't find any links to old patches on your web site...
> > [...]
>
> I only keep around patches to the last official kernel, plus the latest
> -pre and -ac I patched. Since the patch itself is being updated, its a
> pain to backport to older kernels.
>
No, I'm not asking for backport, just links to one version back just in case
the latest patch has a bug much like this...
I'd rather run one (working) version back than have to go to UP just to get
preempt... Needless to say, I chose to keep smp.
Mike
next prev parent reply other threads:[~2001-10-10 5:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 4:46 Compile Filure on 2.4.10-ac10+preempt+smp Mike Fedyk
2001-10-10 5:15 ` Robert Love
2001-10-10 5:24 ` Mike Fedyk [this message]
2001-10-10 5:34 ` Robert Love
2001-10-10 6:00 ` Mike Fedyk
2001-10-10 22:52 ` Mike Fedyk
2001-10-10 23:06 ` 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=20011009222403.A12825@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