From: Andreas Schwab <schwab@suse.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Ian Grant <Ian.Grant@cl.cam.ac.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.10 build failure - atomic_dec_and_lock export
Date: 02 Oct 2001 18:39:57 +0200 [thread overview]
Message-ID: <jepu86j8rm.fsf@sykes.suse.de> (raw)
In-Reply-To: <E15oRJg-00005z-00@wisbech.cl.cam.ac.uk> <shs669yvwty.fsf@charged.uio.no>
In-Reply-To: <shs669yvwty.fsf@charged.uio.no> (Trond Myklebust's message of "02 Oct 2001 18:19:21 +0200")
Trond Myklebust <trond.myklebust@fys.uio.no> writes:
|> >>>>> " " == Ian Grant <Ian.Grant@cl.cam.ac.uk> writes:
|>
|> > Trond,
|> > 2.4.10 won't link with CONFIG_SMP and i386 CPU selected. I
|> > believe the problem
|> > lies in in the #ifndef atomic_dec_and_lock in
|> > lib/dec_and_lock.c. As far as I can see this symbol is always
|> > defined because it's exported.
|>
|> This patch looks very redundant.
|>
|> If you have CONFIG_SMP defined then atomic_dec_and_lock will never get
|> defined
Unless you use CONFIG_MODVERSIONS, which causes atomic_dec_and_lock to be
versioned and defined as a macro via <linux/modversions.h>.
Andreas.
--
Andreas Schwab "And now for something
Andreas.Schwab@suse.de completely different."
SuSE Labs, SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
next prev parent reply other threads:[~2001-10-02 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-02 15:18 2.4.10 build failure - atomic_dec_and_lock export Ian Grant
2001-10-02 16:19 ` Trond Myklebust
2001-10-02 16:39 ` Andreas Schwab [this message]
2001-10-02 17:52 ` Trond Myklebust
2001-10-03 2:52 ` [patch] " Keith Owens
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=jepu86j8rm.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=Ian.Grant@cl.cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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