From: kernel test robot <lkp@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Greg Ungerer <gerg@linux-m68k.org>,
Sasha Levin <sashal@kernel.org>
Subject: [linux-stable-rc:linux-5.14.y 717/2116] drivers/mmc/host/wbsd.c:212:28: error: implicit declaration of function 'claim_dma_lock'
Date: Tue, 9 Nov 2021 03:37:00 +0800 [thread overview]
Message-ID: <202111090343.7oZKw1ln-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5357 bytes --]
Hi Arnd,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.14.y
head: 3dfa869cb79d60a2fe66efb4a11517ec7c89de16
commit: 3afd2af53a59327caf21aaadbf5c9b6f3fc0117b [717/2116] m68knommu: only set CONFIG_ISA_DMA_API for ColdFire sub-arch
config: m68k-randconfig-r021-20210927 (attached as .config)
compiler: m68k-linux-gcc (GCC) 11.2.0
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://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?id=3afd2af53a59327caf21aaadbf5c9b6f3fc0117b
git remote add linux-stable-rc https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git fetch --no-tags linux-stable-rc linux-5.14.y
git checkout 3afd2af53a59327caf21aaadbf5c9b6f3fc0117b
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=m68k
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/mmc/host/wbsd.c: In function 'wbsd_request_end':
>> drivers/mmc/host/wbsd.c:212:28: error: implicit declaration of function 'claim_dma_lock' [-Werror=implicit-function-declaration]
212 | dmaflags = claim_dma_lock();
| ^~~~~~~~~~~~~~
>> drivers/mmc/host/wbsd.c:215:17: error: implicit declaration of function 'release_dma_lock'; did you mean 'release_task'? [-Werror=implicit-function-declaration]
215 | release_dma_lock(dmaflags);
| ^~~~~~~~~~~~~~~~
| release_task
cc1: some warnings being treated as errors
--
sound/core/isadma.c: In function 'snd_dma_program':
>> sound/core/isadma.c:33:17: error: implicit declaration of function 'claim_dma_lock' [-Werror=implicit-function-declaration]
33 | flags = claim_dma_lock();
| ^~~~~~~~~~~~~~
>> sound/core/isadma.c:41:9: error: implicit declaration of function 'release_dma_lock' [-Werror=implicit-function-declaration]
41 | release_dma_lock(flags);
| ^~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/claim_dma_lock +212 drivers/mmc/host/wbsd.c
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 203
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 204 static void wbsd_request_end(struct wbsd_host *host, struct mmc_request *mrq)
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 205 {
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 206 unsigned long dmaflags;
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 207
cfa7f52164d6cd drivers/mmc/wbsd.c Pierre Ossman 2006-01-08 208 if (host->dma >= 0) {
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 209 /*
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 210 * Release ISA DMA controller.
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 211 */
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 @212 dmaflags = claim_dma_lock();
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 213 disable_dma(host->dma);
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 214 clear_dma_ff(host->dma);
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 @215 release_dma_lock(dmaflags);
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 216
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 217 /*
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 218 * Disable DMA on host.
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 219 */
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 220 wbsd_write_index(host, WBSD_IDX_DMA, 0);
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 221 }
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 222
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 223 host->mrq = NULL;
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 224
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 225 /*
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 226 * MMC layer might call back into the driver so first unlock.
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 227 */
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 228 spin_unlock(&host->lock);
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 229 mmc_request_done(host->mmc, mrq);
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 230 spin_lock(&host->lock);
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 231 }
^1da177e4c3f41 drivers/mmc/wbsd.c Linus Torvalds 2005-04-16 232
:::::: The code at line 212 was first introduced by commit
:::::: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Linux-2.6.12-rc2
:::::: TO: Linus Torvalds <torvalds@ppc970.osdl.org>
:::::: CC: Linus Torvalds <torvalds@ppc970.osdl.org>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 31037 bytes --]
reply other threads:[~2021-11-08 19:37 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=202111090343.7oZKw1ln-lkp@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=gerg@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@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®