Commit 04e8429c authored Jul 25, 2023 by James Clark Committed by Suzuki K Poulose Jul 26, 2023

coresight: Fix all W=1 build warnings



The kernel test robot looks for new warnings in a W=1 build, so fix all
the existing warnings to make it easier to spot new ones when building
locally.

The fixes are for undocumented function arguments and an incorrect doc
style.

Signed-off-by: James Clark <james.clark@arm.com>
Reviewed-by: Mike Leach <mike.leach@linaro.org>
Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
Link: https://lore.kernel.org/r/20230725140604.1350406-1-james.clark@arm.com

parent 134124ac

drivers/hwtracing/coresight/coresight-cti-core.c

+1 −1

Original line number	Diff line number	Diff line
		@@ -22,7 +22,7 @@
		#include "coresight-priv.h"
		#include "coresight-cti.h"

		/**
		/*
		* CTI devices can be associated with a PE, or be connected to CoreSight
		* hardware. We have a list of all CTIs irrespective of CPU bound or
		* otherwise.

drivers/hwtracing/coresight/coresight-etm4x-cfg.c

+2 −2

Original line number	Diff line number	Diff line
		@@ -40,7 +40,7 @@
		* Invalid offsets will result in fail code return and feature load failure.
		*
		* @drvdata: driver data to map into.
		* @reg: register to map.
		* @reg_csdev: register to map.
		* @offset: device offset for the register
		*/
		static int etm4_cfg_map_reg_offset(struct etmv4_drvdata *drvdata,
		@@ -132,7 +132,7 @@ static int etm4_cfg_map_reg_offset(struct etmv4_drvdata *drvdata,
		* etm4_cfg_load_feature - load a feature into a device instance.
		*
		* @csdev: An ETMv4 CoreSight device.
		* @feat: The feature to be loaded.
		* @feat_csdev: The feature to be loaded.
		*
		* The function will load a feature instance into the device, checking that
		* the register definitions are valid for the device.