From: johnspaul92 <johns@ti.com>
To: linux-kernel@vger.kernel.org
Subject: why do we need atomic_set_unchecked
Date: Mon, 27 May 2013 00:47:03 -0700 (PDT) [thread overview]
Message-ID: <1369640823167-656004.post@n7.nabble.com> (raw)
When i tried to apply the GrSecurity patch on linux kernel 3.10 and there the
patch actually modifies atomic_set to atomic_set_unchecked. When i checked
the gcc patch to compile this code it just redefines atomic_set as
atomic_set_unchecked. So what is the use of changing the function name.?? Am
I missing something here(i.e have they given a new definition for this
function anywhere else). And i would also like to know what this
function(atomic_set_unchecked. I know about the atomic_set function) is
used for.
--
View this message in context: http://linux-kernel.2935.n7.nabble.com/why-do-we-need-atomic-set-unchecked-tp656004.html
Sent from the Linux Kernel mailing list archive at Nabble.com.
next reply other threads:[~2013-05-27 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 7:47 johnspaul92 [this message]
2013-05-27 8:04 ` richard -rw- weinberger
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=1369640823167-656004.post@n7.nabble.com \
--to=johns@ti.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
all inboxes | Powered by JetHome®