From: "David S. Miller" <davem@redhat.com>
To: rmk@arm.linux.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dereferencing semaphores and atomic_t's
Date: Wed, 02 Oct 2002 03:32:59 -0700 (PDT) [thread overview]
Message-ID: <20021002.033259.10308318.davem@redhat.com> (raw)
In-Reply-To: <20021002111625.B24770@flint.arm.linux.org.uk>
From: Russell King <rmk@arm.linux.org.uk>
Date: Wed, 2 Oct 2002 11:16:26 +0100
Do we really allow this type of layering violation?
No, it should be killed :-)
(There appear to be some circumstances when obtaining the semaphore count is
useful, but shouldn't we provide an architecture helper function to do that
since a semaphore structure _is_ an architecture-defined opaque structure.)
Feel free to make one.
next prev parent reply other threads:[~2002-10-02 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 10:16 Dereferencing semaphores and atomic_t's Russell King
2002-10-02 10:32 ` David S. Miller [this message]
2002-10-02 13:21 ` Alan Cox
2002-10-02 16:46 ` Mike Anderson
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=20021002.033259.10308318.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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