commit 1b6ce93a1ccee8d38bc88a7114abd77dae3410be
Author: Vladimir Sokolovsky <vlad@mellanox.co.il>
Date:   Tue Dec 22 15:22:44 2009 +0200

    Revert "mlx4_core: Added CX3 device IDs"
    
    This reverts commit 6b1c739631ecde05bc674d2351e28d93a6c7f8f4.

commit 2dbe8f24fc424a31ceea533558710c6400b42313
Author: Vladimir Sokolovsky <vlad@mellanox.co.il>
Date:   Tue Dec 22 15:22:39 2009 +0200

    Revert "mlx4_en: Added device ids table"
    
    This reverts commit 6617c6af3326dae1363bcba40158e02d19e02143.

commit 8da853924c888e943787ea5646a4173df12fd809
Author: Signed-off-by: David Wilder <dwilder@us.ibm.com>
Date:   Mon Dec 21 16:16:49 2009 +0200

    IPoIB: Clear ipoib_neigh.dgid in ipoib_neigh_alloc()
    
    IPoIB can miss a change in destination GID under some conditions.  The
    problem is caused when ipoib_neigh->dgid contains a stale address.
    The fix is to set ipoib_neigh->dgid to zero in ipoib_neigh_alloc().
    
    This can happen when a system using bonding on its IPoIB interfaces
    has switched its active interface from interface A to B and back to A.
    The system that fails over will not correctly processes the 2nd
    address change, as described below.
    
    When an address has changed neighbor->ha is updated with the new
    address.  Each neighbor has an associated ipoib_neigh.
    ipoib_neigh->dgid also holds a copy of the remote node's hardware
    address.  When an address changes neighbor->ha is updated by the
    network layer (arp code) with the new address.  IPoIB detects this
    change in ipoib_start_xmit() by comparing neighbor->ha with
    ipoib_neigh->dgid.  The bug is that ipoib_neigh->dgid may already
    contain the new address (A) thus the change from B to A is missed by
    ipoib.  Here is the sequence of events:
    
        ipoib_neigh->dgid = A  and  neighbor->ha = A
    
    The address is switched to B (the first switch)
    
        neighbor->ha = B
    
    The change is seen in ipoib_start_xmit() -- neighbor->ha !=
    ipoib_neigh->dgid so ipoib_neigh is released, and a new one is
    allocated.
    
    The allocator may return the same chunk of memory that was just
    released, therefore ipoib_neigh->dgid still contains A at this point.
    
    ipoib_neigh->dgid should be updated in neigh_add_path(), but if the
    following conditions are true dgid is not updated:
    
            1) __path_find() returns a path
            2) path->ah is NULL
    
    The remote system now switches from address B to A, neighbor->ha is
    updated to A.
    
    Now we have again : ipoib_neigh->dgid = A  and  neighbor->ha = A
    Since the addresses are the same ipoib won't process the change in
    address.  Fix this by zeroing out the dgid field when allocating a new
    struct ipoib_neigh.
    
    Signed-off-by: David Wilder <dwilder@us.ibm.com>
    Signed-off-by: Roland Dreier <rolandd@cisco.com>

commit c5edf35d2baa2ba8169856be56fd6830c5946abe
Author: Ella Podvalny <ella@mellanox.co.il>
Date:   Sun Dec 20 13:07:49 2009 +0200

    kernel_addons: for fcoe RH5.3
    
    Signed-off-by: Ella Podvalny <ella@mellanox.co.il>

commit 9f3ae03fc7f7994ebfcfda0f614a95baf5e8bcb2
Merge: d427319... 85aba0b...
Author: Vladimir Sokolovsky <vlad@mellanox.co.il>
Date:   Sun Dec 20 13:44:27 2009 +0200

    Merge branch 'ofed_kernel_1_5' of git://git.openfabrics.org/~amirv/ofed_1_5 into ofed_kernel_1_5

commit 85aba0b72f16ad16c55bae1f1c8fd5ca485a4882
Author: Amir Vadai <amirv@mellanox.co.il>
Date:   Sun Dec 20 13:23:28 2009 +0200

    sdp: fixed compilation warning
    
    Signed-off-by: Amir Vadai <amirv@mellanox.co.il>

commit 84ebd9f8515b5eca679e5baa9ea460d85cc9ac09
Author: Amir Vadai <amirv@mellanox.co.il>
Date:   Sun Dec 20 11:45:37 2009 +0200

    sdp: ZCopy SrcAvail payload size limit fixed + fix ZCopy rx for small packets
    
    Signed-off-by: Amir Vadai <amirv@mellanox.co.il>

commit d4273197d3002e3ba6001e8392acdc86cd73fdbc
Author: Ella Podvalny <ella@mellanox.co.il>
Date:   Sun Dec 20 10:22:27 2009 +0200

    kernel_addons: for fcoe SLES11
    
    Signed-off-by: Ella Podvalny <ella@mellanox.co.il>
