public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: linux-arch@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Sven Eckelmann <sven@narfation.org>,
	Akinobu Mita <akinobu.mita@gmail.com>
Subject: [PATCHv4 03/11] fault_inject: Remove private define of atomic_dec_not_zero
Date: Wed, 27 Jul 2011 11:47:42 +0200	[thread overview]
Message-ID: <1311760070-21532-3-git-send-email-sven@narfation.org> (raw)
In-Reply-To: <1311760070-21532-1-git-send-email-sven@narfation.org>

atomic_dec_not_zero is defined through <linux/atomic.h> for all
architectures and fault_inject doesn't need an extra define which may
collide with the global one.

Signed-off-by: Sven Eckelmann <sven@narfation.org>
Cc: Akinobu Mita <akinobu.mita@gmail.com>
---
 lib/fault-inject.c |    2 --
 1 files changed, 0 insertions(+), 2 deletions(-)

diff --git a/lib/fault-inject.c b/lib/fault-inject.c
index 2577b12..8ce98c6 100644
--- a/lib/fault-inject.c
+++ b/lib/fault-inject.c
@@ -45,8 +45,6 @@ static void fail_dump(struct fault_attr *attr)
 		dump_stack();
 }
 
-#define atomic_dec_not_zero(v)		atomic_add_unless((v), -1, 0)
-
 static bool fail_task(struct fault_attr *attr, struct task_struct *task)
 {
 	return !in_interrupt() && task->make_it_fail;
-- 
1.7.5.4

  parent reply	other threads:[~2011-07-27  9:47 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27  9:47 [PATCHv4 01/11] atomic: add *_dec_not_zero Sven Eckelmann
     [not found] ` <1311760070-21532-1-git-send-email-sven-KaDOiPu9UxWEi8DpZVb4nw@public.gmane.org>
2011-07-27  9:47   ` [PATCHv4 02/11] batman-adv: Remove private define of atomic_dec_not_zero Sven Eckelmann
2011-07-27  9:47     ` Sven Eckelmann
2011-07-27  9:47 ` Sven Eckelmann [this message]
2011-07-27  9:47   ` [PATCHv4 03/11] fault_inject: " Sven Eckelmann
2011-07-27  9:47 ` [PATCHv4 04/11] PM: Use *_dec_not_zero instead of *_add_unless Sven Eckelmann
2011-07-27 19:50   ` Rafael J. Wysocki
2011-07-27 20:36     ` Pavel Machek
2011-07-27 20:36       ` Pavel Machek
2011-07-28 21:43       ` Rafael J. Wysocki
2011-07-28 21:43         ` Rafael J. Wysocki
2011-07-27  9:47 ` [PATCHv4 05/11] omap3isp: " Sven Eckelmann
2011-07-27  9:47   ` Sven Eckelmann
2011-07-31 15:00   ` Laurent Pinchart
2011-08-01 10:07     ` Sven Eckelmann
2011-08-01 11:10       ` Laurent Pinchart
2011-08-01 11:10         ` Laurent Pinchart
2011-07-27  9:47 ` [PATCHv4 06/11] qeth: " Sven Eckelmann
2011-07-27  9:47   ` Sven Eckelmann
2011-07-27  9:47 ` [PATCHv4 07/11] ext4: " Sven Eckelmann
2011-07-27  9:47   ` Sven Eckelmann
2011-07-27  9:47 ` [PATCHv4 08/11] xfs: " Sven Eckelmann
2011-07-27  9:47   ` Sven Eckelmann
2011-07-27  9:47 ` [PATCHv4 09/11] memcg: " Sven Eckelmann
2011-07-27  9:47   ` Sven Eckelmann
2011-07-27 11:58   ` Michal Hocko
2011-07-27  9:47 ` [PATCHv4 10/11] drop_monitor: " Sven Eckelmann
2011-07-27  9:47   ` Sven Eckelmann
2011-07-27 10:59   ` Neil Horman
2011-07-27 10:59     ` Neil Horman
2011-07-27 11:52     ` Sven Eckelmann
2011-07-27 14:25       ` Neil Horman
2011-07-27 14:25         ` Neil Horman
2011-07-27  9:47 ` [PATCHv4 11/11] Phonet: " Sven Eckelmann
2011-07-27  9:47   ` Sven Eckelmann
2011-07-27 10:29   ` Rémi Denis-Courmont
2011-08-02  9:58 ` [PATCHv4 01/11] atomic: add *_dec_not_zero Ralf Baechle

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=1311760070-21532-3-git-send-email-sven@narfation.org \
    --to=sven@narfation.org \
    --cc=akinobu.mita@gmail.com \
    --cc=linux-arch@vger.kernel.org \
    --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