public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Kaiwei Liu <kaiwei.liu@unisoc.com>, Vinod Koul <vkoul@kernel.org>,
	Orson Zhai <orsonzhai@gmail.com>,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	Chunyan Zhang <zhang.lyra@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, dmaengine@vger.kernel.org,
	linux-kernel@vger.kernel.org, kaiwei liu <liukaiwei086@gmail.com>,
	Wenming Wu <wenming.wu@unisoc.com>
Subject: Re: [PATCH 1/3] dmaengine: sprd: support dma device suspend/resume
Date: Thu, 26 Oct 2023 01:46:03 +0800	[thread overview]
Message-ID: <202310260136.yDATuOfv-lkp@intel.com> (raw)
In-Reply-To: <20231025120500.8914-1-kaiwei.liu@unisoc.com>

Hi Kaiwei,

kernel test robot noticed the following build warnings:

[auto build test WARNING on vkoul-dmaengine/next]
[also build test WARNING on linus/master v6.6-rc7 next-20231025]
[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/Kaiwei-Liu/dmaengine-sprd-delete-enable-opreation-in-probe/20231025-201524
base:   https://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine.git next
patch link:    https://lore.kernel.org/r/20231025120500.8914-1-kaiwei.liu%40unisoc.com
patch subject: [PATCH 1/3] dmaengine: sprd: support dma device suspend/resume
config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20231026/202310260136.yDATuOfv-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231026/202310260136.yDATuOfv-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/202310260136.yDATuOfv-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/dma/sprd-dma.c: In function 'sprd_dma_suspend_noirq':
   drivers/dma/sprd-dma.c:1296:38: error: 'struct dev_pm_info' has no member named 'usage_count'
    1296 |             (atomic_read(&(dev->power.usage_count)) > 1))
         |                                      ^
   drivers/dma/sprd-dma.c: In function 'sprd_dma_resume_early':
   drivers/dma/sprd-dma.c:1305:38: error: 'struct dev_pm_info' has no member named 'usage_count'
    1305 |             (atomic_read(&(dev->power.usage_count)) > 1))
         |                                      ^
   drivers/dma/sprd-dma.c: At top level:
>> drivers/dma/sprd-dma.c:1302:12: warning: 'sprd_dma_resume_early' defined but not used [-Wunused-function]
    1302 | static int sprd_dma_resume_early(struct device *dev)
         |            ^~~~~~~~~~~~~~~~~~~~~
>> drivers/dma/sprd-dma.c:1293:12: warning: 'sprd_dma_suspend_noirq' defined but not used [-Wunused-function]
    1293 | static int sprd_dma_suspend_noirq(struct device *dev)
         |            ^~~~~~~~~~~~~~~~~~~~~~


vim +/sprd_dma_resume_early +1302 drivers/dma/sprd-dma.c

  1292	
> 1293	static int sprd_dma_suspend_noirq(struct device *dev)
  1294	{
  1295		if ((pm_runtime_status_suspended(dev)) ||
  1296		    (atomic_read(&(dev->power.usage_count)) > 1))
  1297			return 0;
  1298	
  1299		return sprd_dma_runtime_suspend(dev);
  1300	}
  1301	
> 1302	static int sprd_dma_resume_early(struct device *dev)
  1303	{
  1304		if ((pm_runtime_status_suspended(dev)) ||
  1305		    (atomic_read(&(dev->power.usage_count)) > 1))
  1306			return 0;
  1307	
  1308		return sprd_dma_runtime_resume(dev);
  1309	}
  1310	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2023-10-25 17:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25 12:05 [PATCH 1/3] dmaengine: sprd: support dma device suspend/resume Kaiwei Liu
2023-10-25 17:46 ` kernel test robot [this message]
2023-11-01 13:01 ` kernel test robot

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=202310260136.yDATuOfv-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=kaiwei.liu@unisoc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liukaiwei086@gmail.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=orsonzhai@gmail.com \
    --cc=vkoul@kernel.org \
    --cc=wenming.wu@unisoc.com \
    --cc=zhang.lyra@gmail.com \
    /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