From: Robert Love <rml@tech9.net>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Compile Filure on 2.4.10-ac10+preempt+smp
Date: 10 Oct 2001 01:34:41 -0400 [thread overview]
Message-ID: <1002692093.1243.238.camel@phantasy> (raw)
In-Reply-To: <20011009222403.A12825@mikef-linux.matchmail.com>
In-Reply-To: <20011009214655.A26663@mikef-linux.matchmail.com> <1002690949.862.233.camel@phantasy> <20011009222403.A12825@mikef-linux.matchmail.com>
On Wed, 2001-10-10 at 01:24, Mike Fedyk wrote:
> On Wed, Oct 10, 2001 at 01:15:25AM -0400, Robert Love wrote:
> >
> > 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...
Let me know, I didn't test :)
If it works I will merge it...
> > 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.
OK, then try editing the URL, I scp the patches in and don't ssh in and
actually clean the stuff up but every here and there.
ie, change the ac10 to ac9 in the URL.
The ChangeLog should tell you when a change occured that broke
something. This changed happened during 2.4.10-ac5 (unless some later
-ac added the second spin_unlock define).
next prev parent reply other threads:[~2001-10-10 5:34 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
2001-10-10 5:34 ` Robert Love [this message]
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=1002692093.1243.238.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.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