From: kernel test robot <lkp@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, Vinod Koul <vkoul@kernel.org>
Subject: drivers/dma/ste_dma40.c:57: warning: Excess struct member 'dev_tx' description in 'stedma40_platform_data'
Date: Sun, 17 Dec 2023 14:22:08 +0800 [thread overview]
Message-ID: <202312171417.izbQThoU-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 3b8a9b2e6809d281890dd0a1102dc14d2cd11caf
commit: 42ae6f1695beed57958e7a2554e6d52dddc56e43 dmaengine: ste_dma40: Remove platform data
date: 7 months ago
config: arm-defconfig (https://download.01.org/0day-ci/archive/20231217/202312171417.izbQThoU-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project.git f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231217/202312171417.izbQThoU-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202312171417.izbQThoU-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/dma/ste_dma40.c:57: warning: Excess struct member 'dev_tx' description in 'stedma40_platform_data'
>> drivers/dma/ste_dma40.c:57: warning: Excess struct member 'dev_rx' description in 'stedma40_platform_data'
drivers/dma/ste_dma40.c:151: warning: expecting prototype for enum 40_command. Prototype was for enum d40_command instead
vim +57 drivers/dma/ste_dma40.c
30
31 /**
32 * struct stedma40_platform_data - Configuration struct for the dma device.
33 *
34 * @dev_tx: mapping between destination event line and io address
35 * @dev_rx: mapping between source event line and io address
36 * @disabled_channels: A vector, ending with -1, that marks physical channels
37 * that are for different reasons not available for the driver.
38 * @soft_lli_chans: A vector, that marks physical channels will use LLI by SW
39 * which avoids HW bug that exists in some versions of the controller.
40 * SoftLLI introduces relink overhead that could impact performace for
41 * certain use cases.
42 * @num_of_soft_lli_chans: The number of channels that needs to be configured
43 * to use SoftLLI.
44 * @use_esram_lcla: flag for mapping the lcla into esram region
45 * @num_of_memcpy_chans: The number of channels reserved for memcpy.
46 * @num_of_phy_chans: The number of physical channels implemented in HW.
47 * 0 means reading the number of channels from DMA HW but this is only valid
48 * for 'multiple of 4' channels, like 8.
49 */
50 struct stedma40_platform_data {
51 int disabled_channels[STEDMA40_MAX_PHYS];
52 int *soft_lli_chans;
53 int num_of_soft_lli_chans;
54 bool use_esram_lcla;
55 int num_of_memcpy_chans;
56 int num_of_phy_chans;
> 57 };
58
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-17 6:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202312171417.izbQThoU-lkp@intel.com \
--to=lkp@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vkoul@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®