The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: kakadu_croc@yahoo.com
Cc: bcrl@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: brlock_is_locked()?
Date: Wed, 22 Aug 2001 11:03:16 -0700 (PDT)	[thread overview]
Message-ID: <20010822.110316.57459277.davem@redhat.com> (raw)
In-Reply-To: <20010822180056.58350.qmail@web10902.mail.yahoo.com>
In-Reply-To: <Pine.LNX.4.33.0108221231260.19638-100000@touchme.toronto.redhat.com> <20010822180056.58350.qmail@web10902.mail.yahoo.com>

   From: Brad Chapman <kakadu_croc@yahoo.com>
   Date: Wed, 22 Aug 2001 11:00:56 -0700 (PDT)

   	I'm not talking about _who_ owns the lock, I'm talking about whether
   the lock itself is locked. I don't care which process is using the lock;
   I just want to know if _somebody_ is using it. Is this possible?

Show a valid use for such a boolean state, then
the discussion may proceed :-)

Later,
David S. Miller
davem@redhat.com

  reply	other threads:[~2001-08-22 18:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-22 13:04 brlock_is_locked()? Brad Chapman
2001-08-22 16:33 ` brlock_is_locked()? Ben LaHaise
2001-08-22 18:00   ` brlock_is_locked()? Brad Chapman
2001-08-22 18:03     ` David S. Miller [this message]
2001-08-22 18:17       ` brlock_is_locked()? Brad Chapman
2001-08-22 18:26         ` brlock_is_locked()? David S. Miller
2001-08-22 18:33           ` brlock_is_locked()? Brad Chapman
2001-08-22 18:47             ` brlock_is_locked()? David S. Miller
2001-08-22 18:53               ` brlock_is_locked()? Brad Chapman
2001-08-22 19:00                 ` brlock_is_locked()? David S. Miller
2001-08-22 19:08                   ` brlock_is_locked()? Brad Chapman
2001-08-24  6:49                     ` brlock_is_locked()? Jens Axboe
2001-08-24 14:11                       ` brlock_is_locked()? Brad Chapman

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=20010822.110316.57459277.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=bcrl@redhat.com \
    --cc=kakadu_croc@yahoo.com \
    --cc=linux-kernel@vger.kernel.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