提交 dd42a088 编写于 作者: M Mark Rutland 提交者: Jiri Kosina

Docs: this_cpu_ops: remove redundant add forms

Commit ac490f4d (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: NMark Rutland <mark.rutland@arm.com>
Reviewed-by: NPranith Kumar <bobby.prani@gmail.com>
Acked-by: NChristoph Lameter <cl@linux.com>
Signed-off-by: NRandy Dunlap <rdunlap@infradead.org>
Signed-off-by: NJiri Kosina <jkosina@suse.cz>
上级 25b91ac2
...@@ -41,7 +41,6 @@ The following this_cpu() operations with implied preemption protection ...@@ -41,7 +41,6 @@ The following this_cpu() operations with implied preemption protection
are defined. These operations can be used without worrying about are defined. These operations can be used without worrying about
preemption and interrupts. preemption and interrupts.
this_cpu_add()
this_cpu_read(pcp) this_cpu_read(pcp)
this_cpu_write(pcp, val) this_cpu_write(pcp, val)
this_cpu_add(pcp, val) this_cpu_add(pcp, val)
...@@ -225,7 +224,6 @@ still occur while an operation is in progress and if the interrupt too ...@@ -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 modifies the variable, then RMW actions can not be guaranteed to be
safe. safe.
__this_cpu_add()
__this_cpu_read(pcp) __this_cpu_read(pcp)
__this_cpu_write(pcp, val) __this_cpu_write(pcp, val)
__this_cpu_add(pcp, val) __this_cpu_add(pcp, val)
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册