From: sanjeev sharma <sanjeevsharmaengg@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Is spin_is_locked() safe to use with BUG_ON()/WARN_ON()?
Date: Sun, 10 Aug 2014 23:41:53 -0700 (PDT) [thread overview]
Message-ID: <1407739313377-921802.post@n7.nabble.com> (raw)
In-Reply-To: <CA+55aFww-UYfLA4cN6MSkeXzmAnAruShddAPegCpn+5yd1HGmQ@mail.gmail.com>
Hello All,
I think still this is not being replaced with assert_spin_lock_held() call
as suggested by Linus.It is worth to replace these calls.
Sanjeev Sharma
--
View this message in context: http://linux-kernel.2935.n7.nabble.com/Is-spin-is-locked-safe-to-use-with-BUG-ON-WARN-ON-tp654800p921802.html
Sent from the Linux Kernel mailing list archive at Nabble.com.
next prev parent reply other threads:[~2014-08-11 6:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 14:50 David Howells
2013-05-23 14:59 ` Linus Torvalds
2014-08-11 6:41 ` sanjeev sharma [this message]
2013-05-23 15:12 ` David Howells
2013-05-24 1:29 ` Ryan Mallon
2013-05-28 8:07 ` Ingo Molnar
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=1407739313377-921802.post@n7.nabble.com \
--to=sanjeevsharmaengg@gmail.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
Powered by JetHome