Docs: this_cpu_ops: remove redundant add forms

Commit ac490f4dca94 (Documentation: this_cpu_ops.txt: Update description
of this_cpu_ops) added lists of {__,}this_cpu operations, but these have
duplicate, parameter-less entries for {__,}this_cpu_add which don't
correspond to any implementation. No other operations have such
duplicate entries.

Given both are also listed with their full complement of arguments, the
empty forms are redundant and can be removed. This patch performs said
removal.

Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Reviewed-by: Pranith Kumar <bobby.prani@gmail.com>
Acked-by: Christoph Lameter <cl@linux.com>
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>

diff --git a/Documentation/this_cpu_ops.txt b/Documentation/this_cpu_ops.txt
index 0ec995712176ed83d4dd04ecfed81aa442848c07..2cbf71975381d0a850d1a254aa76af7957b35058 100644 (file)
--- a/Documentation/this_cpu_ops.txt
+++ b/Documentation/this_cpu_ops.txt
@@ -41,7 +41,6 @@ The following this_cpu() operations with implied preemption protection
 are defined. These operations can be used without worrying about
 preemption and interrupts.
 
-       this_cpu_add()
        this_cpu_read(pcp)
        this_cpu_write(pcp, val)
        this_cpu_add(pcp, val)
@@ -225,7 +224,6 @@ still occur while an operation is in progress and if the interrupt too
 modifies the variable, then RMW actions can not be guaranteed to be
 safe.
 
-       __this_cpu_add()
        __this_cpu_read(pcp)
        __this_cpu_write(pcp, val)
        __this_cpu_add(pcp, val)