All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <roland@topspin.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Sparse "context" checking..
Date: Sat, 30 Oct 2004 21:11:24 -0700	[thread overview]
Message-ID: <52d5yzwmqb.fsf@topspin.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0410302005270.28839@ppc970.osdl.org> (Linus Torvalds's message of "Sat, 30 Oct 2004 20:20:53 -0700 (PDT)")

    Linus> In particular, this is designed for doing things like
    Linus> matching up a "lock" with the pairing "unlock", and right
    Linus> now that's exactly what the code does: it makes each
    Linus> spinlock count as "+1" in the context, and each spinunlock
    Linus> count as "-1", and then hopefully it should all add up.

Do you have a plan for how to handle functions like spin_trylock()?  I
notice in the current tree you just didn't annotate spin_trylock().

Thanks,
  Roland

  reply	other threads:[~2004-10-31  4:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-31  3:20 Sparse "context" checking Linus Torvalds
2004-10-31  4:11 ` Roland Dreier [this message]
2004-10-31  5:03   ` Linus Torvalds
2004-11-11 19:38 ` Greg KH

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=52d5yzwmqb.fsf@topspin.com \
    --to=roland@topspin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.