Re: [PATCH v2 1/3] locking: Document the semantics of spin_is_locked()

From: Christoph Hellwig
Date: Thu Apr 05 2018 - 03:48:00 EST

Next message: Joonsoo Kim: "Re: [lkp-robot] [mm/cma] 2b0f904a5a: fio.read_bw_MBps -16.1% regression"
Previous message: Joonsoo Kim: "Re: [PATCH v1] mm: help the ALLOC_HARDER allocation pass the watermarki when CMA on"
In reply to: David Howells: "Re: [PATCH v2 1/3] locking: Document the semantics of spin_is_locked()"
Next in thread: Andrea Parri: "Re: [PATCH v2 1/3] locking: Document the semantics of spin_is_locked()"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Can't we just kill off spin_is_locked? It seems pretty much all uses
should simply be replaced with lockdep annotations, and there aren't
many to start with.

Next message: Joonsoo Kim: "Re: [lkp-robot] [mm/cma] 2b0f904a5a: fio.read_bw_MBps -16.1% regression"
Previous message: Joonsoo Kim: "Re: [PATCH v1] mm: help the ALLOC_HARDER allocation pass the watermarki when CMA on"
In reply to: David Howells: "Re: [PATCH v2 1/3] locking: Document the semantics of spin_is_locked()"
Next in thread: Andrea Parri: "Re: [PATCH v2 1/3] locking: Document the semantics of spin_is_locked()"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]