public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dipankar Sarma <dipankar@in.ibm.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.39-mm1 fixes 2/3
Date: Mon, 30 Sep 2002 16:45:47 +0530	[thread overview]
Message-ID: <20020930164547.B27121@in.ibm.com> (raw)
In-Reply-To: <20020930164314.A27121@in.ibm.com>; from dipankar@in.ibm.com on Mon, Sep 30, 2002 at 04:43:14PM +0530

The read_barrier_depends patch didn't have compilable list_for_each_rcu()
macros. These macros allow a simpler interface to use RCU by taking
care of memory barriers. Fix against 2.5.39-mm1.

Thanks
-- 
Dipankar Sarma  <dipankar@in.ibm.com> http://lse.sourceforge.net
Linux Technology Center, IBM Software Lab, Bangalore, India.


--- include/linux/list.h.orig	Mon Sep 30 13:59:10 2002
+++ include/linux/list.h	Mon Sep 30 13:59:23 2002
@@ -307,7 +307,7 @@
  */
 #define list_for_each_rcu(pos, head) \
 	for (pos = (head)->next, prefetch(pos->next); pos != (head); \
-        	pos = pos->next, ({ read_barrier_depends(); 0}), prefetch(pos->next))
+        	pos = pos->next, ({ read_barrier_depends(); 0;}), prefetch(pos->next))
         	
 /**
  * list_for_each_safe_rcu	-	iterate over an rcu-protected list safe
@@ -318,7 +318,7 @@
  */
 #define list_for_each_safe_rcu(pos, n, head) \
 	for (pos = (head)->next, n = pos->next; pos != (head); \
-		pos = n, ({ read_barrier_depends(); 0}), n = pos->next)
+		pos = n, ({ read_barrier_depends(); 0;}), n = pos->next)
 
 #endif /* __KERNEL__ || _LVM_H_INCLUDE */
 

  reply	other threads:[~2002-09-30 11:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-30 11:13 [PATCH] 2.5.39-mm1 fixes 1/3 Dipankar Sarma
2002-09-30 11:15 ` Dipankar Sarma [this message]
2002-09-30 11:17   ` [PATCH] 2.5.39-mm1 fixes 3/3 Dipankar Sarma

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=20020930164547.B27121@in.ibm.com \
    --to=dipankar@in.ibm.com \
    --cc=akpm@zip.com.au \
    --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