From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Why don't we have atomic_set_mask()?
Date: Thu, 17 Mar 2011 12:09:51 +0000 [thread overview]
Message-ID: <20110317120950.GI29758@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTi=V5mHHibKftXZ1A+s6xiuqH5X0pqYPMjZod6EV@mail.gmail.com>
On Thu, Mar 17, 2011 at 08:36:15PM +0900, KyongHo Cho wrote:
> Hi.
>
> arch/arm/asm/atomic.h defines atomic_clear_mask() but its counterpart,
> atomic_set_mask() is not defined.
>
> Don't we need it?
I can't reply to you:
| A message that you sent could not be delivered to one or more of its
| recipients. This is a permanent error. The following address(es) failed:
|
| pullip.cho at samsung.com
| SMTP error from remote mail server after end of data:
| host mailin.samsung.com [203.254.224.12]: 550 esmtp:
| protocol deviation
Which basically means that Samsung's MTA is currently broken.
next prev parent reply other threads:[~2011-03-17 12:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 11:36 Why don't we have atomic_set_mask()? KyongHo Cho
2011-03-17 12:07 ` Russell King - ARM Linux
2011-03-17 13:25 ` Detlef Vollmann
2011-03-17 12:09 ` Russell King - ARM Linux [this message]
2011-03-17 12:24 ` KyongHo Cho
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=20110317120950.GI29758@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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