From: kernel test robot <lkp@intel.com>
To: Daniel Palmer <daniel@0x0f.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chenxing:mstar_v6_5_reorder 363/700] drivers/dma/mstar/mstar-msc313-bdma.c:782:13: warning: unused variable 'ret'
Date: Wed, 29 Jul 2026 22:51:01 +0800 [thread overview]
Message-ID: <202607292228.jMoOE7k1-lkp@intel.com> (raw)
tree: https://github.com/linux-chenxing/linux.git mstar_v6_5_reorder
head: 1a5c60e65ea399670a5384b869c4958338af2799
commit: 26178975043b0a83d96b42a14c44bb70fdb84d4b [363/700] dma: mstar: msc313 bdma driver
config: arc-allmodconfig (https://download.01.org/0day-ci/archive/20260729/202607292228.jMoOE7k1-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260729/202607292228.jMoOE7k1-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/202607292228.jMoOE7k1-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/dma/mstar/mstar-msc313-bdma.c: In function 'msc313_bdma_remove':
>> drivers/dma/mstar/mstar-msc313-bdma.c:782:13: warning: unused variable 'ret' [-Wunused-variable]
782 | int ret, i;
| ^~~
drivers/dma/mstar/mstar-msc313-bdma.c:781:24: warning: unused variable 'dev' [-Wunused-variable]
781 | struct device *dev = &pdev->dev;
| ^~~
vim +/ret +782 drivers/dma/mstar/mstar-msc313-bdma.c
777
778 static int msc313_bdma_remove(struct platform_device *pdev)
779 {
780 struct msc313_bdma *bdma = platform_get_drvdata(pdev);
781 struct device *dev = &pdev->dev;
> 782 int ret, i;
783
784 of_dma_controller_free(pdev->dev.of_node);
785
786 for (i = 0; i < bdma->info->channels; i++){
787 struct msc313_bdma_chan *chan = &bdma->chans[i];
788 tasklet_kill(&chan[i].tasklet);
789 }
790
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-29 14:51 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=202607292228.jMoOE7k1-lkp@intel.com \
--to=lkp@intel.com \
--cc=daniel@0x0f.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.