Unverified Commit e634ff77 authored Mar 28, 2022 by Randy Dunlap Committed by Palmer Dabbelt Mar 31, 2022

riscv: cpu.c: don't use kernel-doc markers for comments

Repair kernel-doc build warnings caused by using "/**" kernel-doc
markers for comments that are not in kernel-doc format:

cpu.c:89: warning: cannot understand function prototype: 'struct riscv_isa_ext_data isa_ext_arr[] = '
cpu.c:114: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst

Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Reported-by: kernel test robot <lkp@intel.com>
Reviewed-by: Atish Patra <atishp@rivosinc.com>
Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

parent 2e7451fb

arch/riscv/kernel/cpu.c

+2 −2

Original line number	Diff line number	Diff line
		@@ -69,7 +69,7 @@ int riscv_of_parent_hartid(struct device_node *node)
		.uprop = #UPROP, \
		.isa_ext_id = EXTID, \
		}
		/**
		/*
		* Here are the ordering rules of extension naming defined by RISC-V
		* specification :
		* 1. All extensions should be separated from other multi-letter extensions
		@@ -110,7 +110,7 @@ static void print_isa_ext(struct seq_file *f)
		}
		}

		/**
		/*
		* These are the only valid base (single letter) ISA extensions as per the spec.
		* It also specifies the canonical order in which it appears in the spec.
		* Some of the extension may just be a place holder for now (B, K, P, J).