Hi Peter, Ingo, I see that in the drivers there are the following types of cmpxchg API:
__cmpxchg64() atomic_cmpxchg() atomic64_cmpxchg() cmpxchg() atomic_long_cmpxchg() cmpxchg_local() local_cmpxchg()(in kernel/events/ring_buffer.c) this_cpu_cmpxchg() Since cmpxchg() internally handles the width, do you think it makes sense to replace the above uses of cmpxchg with the document API (cmpxchg, atomic_cmpxchg, cmpxchg_local)? I am willing to do this and wanted to know if it something you think is worth pursuing. Regards, Pranith -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
