From: "Luis R. Rodriguez" <[email protected]>

For older kernels this is simply a matter of using
LIST_HEAD.

mcgrof@frijol ~/linux-stable (git::master)$ git describe --contains 2955b47d
v3.6-rc1~103^2~4

commit 2955b47d2c1983998a8c5915cb96884e67f7cb53
Author: Dan Williams <[email protected]>
Date:   Mon Jul 9 19:33:25 2012 -0700

    [SCSI] async: introduce 'async_domain' type

    This is in preparation for teaching async_synchronize_full() to sync all
    pending async work, and not just on the async_running domain.  This
    conversion is functionally equivalent, just embedding the existing list
    in a new async_domain type.

    The .registered attribute is used in a later patch to distinguish
    between domains that want to be flushed by async_synchronize_full()
    versus those that only expect async_synchronize_{full|cookie}_domain to
    be used for flushing.

    [jejb: add async.h to scsi_priv.h for struct async_domain]
    Signed-off-by: Dan Williams <[email protected]>
    Acked-by: Arjan van de Ven <[email protected]>
    Acked-by: Mark Brown <[email protected]>
    Tested-by: Eldad Zack <[email protected]>
    Signed-off-by: James Bottomley <[email protected]>

Signed-off-by: Luis R. Rodriguez <[email protected]>
---
 backport/include/linux/compat-3.6.h |    3 +++
 1 file changed, 3 insertions(+)

diff --git a/backport/include/linux/compat-3.6.h 
b/backport/include/linux/compat-3.6.h
index 8fddd31..49f4d3b 100644
--- a/backport/include/linux/compat-3.6.h
+++ b/backport/include/linux/compat-3.6.h
@@ -9,6 +9,9 @@
 
 #if (LINUX_VERSION_CODE >= KERNEL_VERSION(3,2,0))
 #include <linux/i2c.h>
+
+#define ASYNC_DOMAIN_EXCLUSIVE(_domain) LIST_HEAD(_domain)
+
 /* Unlocked flavor */
 #define __i2c_transfer LINUX_BACKPORT(__i2c_transfer)
 extern int __i2c_transfer(struct i2c_adapter *adap, struct i2c_msg *msgs,
-- 
1.7.10.4

--
To unsubscribe from this list: send the line "unsubscribe backports" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to