linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
Cc: alsa-devel@alsa-project.org,
	Matt Ranostay <matt@ranostay.consulting>,
	Tony Lindgren <tony@atomide.com>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>,
	kbuild-all@01.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH v2] ASoC: omap-mcbsp: Add PM QoS support for McBSP to prevent glitches
Date: Thu, 1 Dec 2016 16:42:45 +0800	[thread overview]
Message-ID: <201612011637.wk2GLNgx%fengguang.wu@intel.com> (raw)
In-Reply-To: <1480467978-20463-1-git-send-email-matt@ranostay.consulting>

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

Hi Matt,

[auto build test ERROR on asoc/for-next]
[also build test ERROR on v4.9-rc7 next-20161130]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Matt-Ranostay/ASoC-omap-mcbsp-Add-PM-QoS-support-for-McBSP-to-prevent-glitches/20161201-095105
base:   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
config: arm-allmodconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
        wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=arm 

All errors (new ones prefixed by >>):

   sound/soc/omap/mcbsp.c: In function 'omap_mcbsp_start':
>> sound/soc/omap/mcbsp.c:653:28: error: 'struct omap_mcbsp' has no member named 'pm_qos_req'; did you mean 'dma_req'?
      pm_qos_add_request(&mcbsp->pm_qos_req,
                               ^~
   sound/soc/omap/mcbsp.c: In function 'omap_mcbsp_stop':
   sound/soc/omap/mcbsp.c:745:30: error: 'struct omap_mcbsp' has no member named 'pm_qos_req'; did you mean 'dma_req'?
     pm_qos_remove_request(&mcbsp->pm_qos_req);
                                 ^~
   sound/soc/omap/mcbsp.c: In function 'omap_mcbsp_cleanup':
   sound/soc/omap/mcbsp.c:1113:34: error: 'struct omap_mcbsp' has no member named 'pm_qos_req'; did you mean 'dma_req'?
     if (pm_qos_request_active(&mcbsp->pm_qos_req))
                                     ^~
   sound/soc/omap/mcbsp.c:1114:31: error: 'struct omap_mcbsp' has no member named 'pm_qos_req'; did you mean 'dma_req'?
      pm_qos_remove_request(&mcbsp->pm_qos_req);
                                  ^~

vim +653 sound/soc/omap/mcbsp.c

   647		int enable_srg = 0;
   648		int latency = mcbsp->pdata->buffer_size * 23;
   649		u16 w;
   650	
   651		/* Prevent omap hardware from hitting off between fifo fills */
   652		if (latency)
 > 653			pm_qos_add_request(&mcbsp->pm_qos_req,
   654					   PM_QOS_CPU_DMA_LATENCY, latency);
   655	
   656		if (mcbsp->st_data)

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 59481 bytes --]

[-- Attachment #3: Type: text/plain, Size: 0 bytes --]



           reply	other threads:[~2016-12-01  8:42 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1480467978-20463-1-git-send-email-matt@ranostay.consulting>]

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=201612011637.wk2GLNgx%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=kbuild-all@01.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=matt@ranostay.consulting \
    --cc=peter.ujfalusi@ti.com \
    --cc=tony@atomide.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).