From: kernel test robot <lkp@intel.com>
To: Amelie Delaunay <amelie.delaunay@foss.st.com>,
Jonathan Corbet <corbet@lwn.net>, Vinod Koul <vkoul@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-doc@vger.kernel.org, dmaengine@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Marek Vasut <marex@denx.de>,
Amelie Delaunay <amelie.delaunay@foss.st.com>
Subject: Re: [PATCH v2 3/4] dmaengine: stm32-dma: add support to trigger STM32 MDMA
Date: Sat, 16 Jul 2022 02:01:20 +0800 [thread overview]
Message-ID: <202207160125.oxFFO8ZQ-lkp@intel.com> (raw)
In-Reply-To: <20220713142148.239253-4-amelie.delaunay@foss.st.com>
Hi Amelie,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on atorgue-stm32/stm32-next]
[also build test WARNING on lwn-2.6/docs-next vkoul-dmaengine/next linus/master v5.19-rc6 next-20220715]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Amelie-Delaunay/STM32-DMA-MDMA-chaining-feature/20220713-222358
base: https://git.kernel.org/pub/scm/linux/kernel/git/atorgue/stm32.git stm32-next
config: hexagon-buildonly-randconfig-r004-20220715 (https://download.01.org/0day-ci/archive/20220716/202207160125.oxFFO8ZQ-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 2da550140aa98cf6a3e96417c87f1e89e3a26047)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/e1f4515659df0475a1e4d6dafd8559771c2b49b0
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Amelie-Delaunay/STM32-DMA-MDMA-chaining-feature/20220713-222358
git checkout e1f4515659df0475a1e4d6dafd8559771c2b49b0
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash drivers/dma/ drivers/iio/adc/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/dma/stm32-dma.c:211: warning: expecting prototype for struct stm32_dma_mdma_cfg. Prototype was for struct stm32_dma_mdma_config instead
vim +211 drivers/dma/stm32-dma.c
199
200 /**
201 * struct stm32_dma_mdma_cfg - STM32 DMA MDMA configuration
202 * @stream_id: DMA request to trigger STM32 MDMA transfer
203 * @ifcr: DMA interrupt flag clear register address,
204 * used by STM32 MDMA to clear DMA Transfer Complete flag
205 * @tcf: DMA Transfer Complete flag
206 */
207 struct stm32_dma_mdma_config {
208 u32 stream_id;
209 u32 ifcr;
210 u32 tcf;
> 211 };
212
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-07-15 18:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 14:21 [PATCH v2 0/4] STM32 DMA-MDMA chaining feature Amelie Delaunay
2022-07-13 14:21 ` [PATCH v2 1/4] docs: arm: stm32: introduce " Amelie Delaunay
2022-07-13 14:21 ` [PATCH v2 2/4] dmaengine: stm32-dmamux: set dmamux channel id in dma features bitfield Amelie Delaunay
2022-07-13 14:21 ` [PATCH v2 3/4] dmaengine: stm32-dma: add support to trigger STM32 MDMA Amelie Delaunay
2022-07-14 19:02 ` Marek Vasut
2022-07-19 15:30 ` Amelie Delaunay
2022-07-15 18:01 ` kernel test robot [this message]
2022-07-13 14:21 ` [PATCH v2 4/4] dmaengine: stm32-mdma: add support to be triggered by STM32 DMA Amelie Delaunay
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=202207160125.oxFFO8ZQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=amelie.delaunay@foss.st.com \
--cc=corbet@lwn.net \
--cc=dmaengine@vger.kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=llvm@lists.linux.dev \
--cc=marex@denx.de \
--cc=mcoquelin.stm32@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).