From: Benjamin Herrenschmidt <bh40@calva.net>
To: <bob@kunk.jriver.com>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: 2.4.0-test10 benh/SMP/spin_trylock
Date: Mon, 20 Nov 2000 21:10:06 +0100 [thread overview]
Message-ID: <19341015134150.13225@192.168.1.2> (raw)
In-Reply-To: <20001120194101.4419.qmail@kunk.jriver.com>
>
>If CONFIG_SMP is not set for the benh devel tree, the ppp_async.c
>file will have an undefined spin_trylock.
Fixed in the current bitkeeper linuxppc_2_3 tree.
None of my rsync tree is currently active. All the important stuff (with
one small exception that should not be important for you) have been merged
in the main trees (linuxppc_2_2 and linuxppc_2_3), including stuff that
was previously only in linuxppc_2_5.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-11-20 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-20 19:41 2.4.0-test10 benh/SMP/spin_trylock bob
2000-11-20 20:10 ` Benjamin Herrenschmidt [this message]
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=19341015134150.13225@192.168.1.2 \
--to=bh40@calva.net \
--cc=bob@kunk.jriver.com \
--cc=linuxppc-dev@lists.linuxppc.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).