From: kbuild test robot <lkp@intel.com>
To: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
Cc: kbuild-all@01.org, Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>, Tejun Heo <tj@kernel.org>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] ASoC: Intel: Remove deprecated create_singlethread_workqueue
Date: Mon, 5 Sep 2016 00:37:17 +0800 [thread overview]
Message-ID: <201609050050.WcsoXPEh%fengguang.wu@intel.com> (raw)
In-Reply-To: <19c71ef6889fa5a09abdea56a4cad083f59b0e64.1473004491.git.bhaktipriya96@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2344 bytes --]
Hi Bhaktipriya,
[auto build test ERROR on asoc/for-next]
[also build test ERROR on v4.8-rc4 next-20160825]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]
url: https://github.com/0day-ci/linux/commits/Bhaktipriya-Shridhar/ASoC-tlv320dac33-Remove-deprecated-create_singlethread_workqueue/20160904-235837
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
config: i386-randconfig-x017-201636 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
sound/soc/intel/atom/sst/sst.c: In function 'intel_sst_suspend':
>> sound/soc/intel/atom/sst/sst.c:445:15: error: incompatible type for argument 1 of 'flush_work'
flush_work(ctx->ipc_post_msg_wq);
^~~
In file included from include/linux/srcu.h:34:0,
from include/linux/notifier.h:15,
from include/linux/memory_hotplug.h:6,
from include/linux/mmzone.h:777,
from include/linux/gfp.h:5,
from include/linux/kmod.h:22,
from include/linux/module.h:13,
from sound/soc/intel/atom/sst/sst.c:22:
include/linux/workqueue.h:444:13: note: expected 'struct work_struct *' but argument is of type 'struct work_struct'
extern bool flush_work(struct work_struct *work);
^~~~~~~~~~
vim +/flush_work +445 sound/soc/intel/atom/sst/sst.c
439 if (stream->status == STREAM_RUNNING) {
440 dev_err(dev, "stream %d is running, can't suspend, abort\n", i);
441 return -EBUSY;
442 }
443 }
444 synchronize_irq(ctx->irq_num);
> 445 flush_work(ctx->ipc_post_msg_wq);
446
447 /* Move the SST state to Reset */
448 sst_set_fw_state_locked(ctx, SST_RESET);
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 28156 bytes --]
prev parent reply other threads:[~2016-09-04 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 15:56 [PATCH v4 0/2] ASoc " Bhaktipriya Shridhar
2016-09-04 15:57 ` [PATCH v4 1/2] ASoC: tlv320dac33: " Bhaktipriya Shridhar
2016-09-04 15:58 ` [PATCH v4 2/2] ASoC: Intel: " Bhaktipriya Shridhar
2016-09-04 16:37 ` kbuild test robot [this message]
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=201609050050.WcsoXPEh%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bhaktipriya96@gmail.com \
--cc=broonie@kernel.org \
--cc=kbuild-all@01.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=tj@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®