linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Lorenzo Bianconi <lorenzo@kernel.org>, nbd@nbd.name
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
	lorenzo.bianconi@redhat.com, linux-wireless@vger.kernel.org,
	sean.wang@mediatek.com
Subject: Re: [PATCH v2 3/5] mt76: mt7663s: rely on mt76_connac_pm_ref/mt76_connac_pm_unref in tx path
Date: Fri, 18 Jun 2021 20:27:53 +0800	[thread overview]
Message-ID: <202106182019.OnhmbPAs-lkp@intel.com> (raw)
In-Reply-To: <b65e861da1a54871c6358766edc81e2f3d9d8233.1624003282.git.lorenzo@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 3677 bytes --]

Hi Lorenzo,

I love your patch! Yet something to improve:

[auto build test ERROR on wireless-drivers/master]
[also build test ERROR on v5.13-rc6 next-20210617]
[cannot apply to wireless-drivers-next/master]
[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]

url:    https://github.com/0day-ci/linux/commits/Lorenzo-Bianconi/mt7663s-enable-runtime-pm-support/20210618-161033
base:   https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers.git master
config: arm-randconfig-r024-20210618 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 64720f57bea6a6bf033feef4a5751ab9c0c3b401)
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
        # install arm cross compiling tool for clang build
        # apt-get install binutils-arm-linux-gnueabi
        # https://github.com/0day-ci/linux/commit/80a27acf098f3392d9b7392c1af5678aa154da72
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Lorenzo-Bianconi/mt7663s-enable-runtime-pm-support/20210618-161033
        git checkout 80a27acf098f3392d9b7392c1af5678aa154da72
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=arm 

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/net/wireless/mediatek/mt76/mt7615/sdio_txrx.c:322:35: error: too many arguments to function call, expected single argument 'pm', have 2 arguments
           mt76_connac_pm_unref(&dev->mphy, &dev->pm);
           ~~~~~~~~~~~~~~~~~~~~             ^~~~~~~~
   drivers/net/wireless/mediatek/mt76/mt7615/../mt76_connac.h:119:1: note: 'mt76_connac_pm_unref' declared here
   mt76_connac_pm_unref(struct mt76_connac_pm *pm)
   ^
   1 error generated.


vim +/pm +322 drivers/net/wireless/mediatek/mt76/mt7615/sdio_txrx.c

   281	
   282	void mt7663s_txrx_worker(struct mt76_worker *w)
   283	{
   284		struct mt76_sdio *sdio = container_of(w, struct mt76_sdio,
   285						      txrx_worker);
   286		struct mt76_dev *mdev = container_of(sdio, struct mt76_dev, sdio);
   287		struct mt7615_dev *dev = container_of(mdev, struct mt7615_dev, mt76);
   288		int i, nframes, ret;
   289	
   290		if (!mt76_connac_pm_ref(&dev->mphy, &dev->pm)) {
   291			queue_work(mdev->wq, &dev->pm.wake_work);
   292			return;
   293		}
   294	
   295		/* disable interrupt */
   296		sdio_claim_host(sdio->func);
   297		sdio_writel(sdio->func, WHLPCR_INT_EN_CLR, MCR_WHLPCR, NULL);
   298	
   299		do {
   300			nframes = 0;
   301	
   302			/* tx */
   303			for (i = 0; i <= MT_TXQ_PSD; i++) {
   304				ret = mt7663s_tx_run_queue(mdev, mdev->phy.q_tx[i]);
   305				if (ret > 0)
   306					nframes += ret;
   307			}
   308			ret = mt7663s_tx_run_queue(mdev, mdev->q_mcu[MT_MCUQ_WM]);
   309			if (ret > 0)
   310				nframes += ret;
   311	
   312			/* rx */
   313			ret = mt7663s_rx_handler(mdev);
   314			if (ret > 0)
   315				nframes += ret;
   316		} while (nframes > 0);
   317	
   318		/* enable interrupt */
   319		sdio_writel(sdio->func, WHLPCR_INT_EN_SET, MCR_WHLPCR, NULL);
   320		sdio_release_host(sdio->func);
   321	
 > 322		mt76_connac_pm_unref(&dev->mphy, &dev->pm);
   323	}
   324	

---
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: 33228 bytes --]

  reply	other threads:[~2021-06-18 12:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18  8:08 [PATCH v2 0/5] mt7663s: enable runtime-pm support Lorenzo Bianconi
2021-06-18  8:08 ` [PATCH v2 1/5] mt76: sdio: do not run mt76_txq_schedule directly Lorenzo Bianconi
2021-06-18  8:08 ` [PATCH v2 2/5] mt76: mt7663s: rely on pm reference counting Lorenzo Bianconi
2021-06-18  8:08 ` [PATCH v2 3/5] mt76: mt7663s: rely on mt76_connac_pm_ref/mt76_connac_pm_unref in tx path Lorenzo Bianconi
2021-06-18 12:27   ` kernel test robot [this message]
2021-06-18  8:08 ` [PATCH v2 4/5] mt76: mt7663s: enable runtime-pm Lorenzo Bianconi
2021-06-18  8:08 ` [PATCH v2 5/5] mt76: mt7615: set macwork timeout according to runtime-pm Lorenzo Bianconi

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=202106182019.OnhmbPAs-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=lorenzo@kernel.org \
    --cc=nbd@nbd.name \
    --cc=sean.wang@mediatek.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;
as well as URLs for NNTP newsgroup(s).