From: Roland Dreier <rdreier@cisco.com>
To: "Pravin Nanaware" <p.nanaware@nihilent.com>
Cc: "John Hubbard" <john.hubbard@gmail.com>,
"LKML" <linux-kernel@vger.kernel.org>
Subject: Re: Bitops source problem
Date: Thu, 17 Jan 2008 11:32:30 -0800 [thread overview]
Message-ID: <adahchcxn75.fsf@cisco.com> (raw)
In-Reply-To: <1145971D427D7F43B0DBDAE22221C4B5035FDDAD@nipns00a210.FPS.NIHILENT.COM> (Pravin Nanaware's message of "Thu, 17 Jan 2008 13:41:20 +0530")
> Yes, indeed none of the atomic bit operations functions has
> LOCK_PREFIX in my version of Linux kernel.
You have a broken source tree then. Where did your kernel source come
from then? I'm not able to find any version of asm-i386/bitops.h
where clear_bit() doesn't have LOCK_PREFIX in any of the trees I
happen to have lying around (which includes some very old trees like 2.4.21)
- R.
next prev parent reply other threads:[~2008-01-17 19:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 8:11 Bitops source problem Pravin Nanaware
2008-01-17 19:32 ` Roland Dreier [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-18 4:40 Pravin Nanaware
2008-01-17 6:38 Pravin Nanaware
2008-01-17 6:44 ` Roland Dreier
2008-01-17 6:59 ` KOSAKI Motohiro
2008-01-17 5:09 Pravin Nanaware
2008-01-17 5:47 ` John Hubbard
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=adahchcxn75.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=john.hubbard@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=p.nanaware@nihilent.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