From: Mark Rutland Date: Thu, 25 Sep 2014 18:23:53 +0000 (-0700) Subject: Docs: this_cpu_ops: remove redundant add forms X-Git-Tag: v3.18-rc1~144^2~7 X-Git-Url: https://openfabrics.org/gitweb/?a=commitdiff_plain;h=dd42a0882a70f10e429b8306dec8aad40babe19c;p=~emulex%2Finfiniband.git 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 Reviewed-by: Pranith Kumar Acked-by: Christoph Lameter Signed-off-by: Randy Dunlap Signed-off-by: Jiri Kosina --- diff --git a/Documentation/this_cpu_ops.txt b/Documentation/this_cpu_ops.txt index 0ec99571217..2cbf7197538 100644 --- 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)