From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, heiko@sntech.de, lgirdwood@gmail.com,
broonie@kernel.org, perex@perex.cz, tiwai@suse.com,
benzh@chromium.org, benchan@google.com, kmixter@google.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
ZhengShunQian <zhengsq@rock-chips.com>
Subject: Re: [PATCH v4 1/2] ASoC: codec: Inno codec driver for RK3036 SoC
Date: Mon, 9 Nov 2015 11:13:54 +0800 [thread overview]
Message-ID: <201511091100.MPMFFAtK%fengguang.wu@intel.com> (raw)
In-Reply-To: <1447035020-10332-2-git-send-email-zhengsq@rock-chips.com>
Hi ZhengShunQian,
[auto build test WARNING on: asoc/for-next]
[also build test WARNING on: v4.3 next-20151106]
url: https://github.com/0day-ci/linux/commits/Shunqian-Zheng/Audio-Codec-Driver-of-RK3036-SoC/20151109-101538
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
coccinelle warnings: (new ones prefixed by >>)
>> sound/soc/codecs/inno_rk3036.c:480:3-8: No need to set .owner here. The core will do it.
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2015-11-09 3:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 2:10 [PATCH v4 0/2] Audio Codec Driver of RK3036 SoC Shunqian Zheng
[not found] ` <1447035020-10332-1-git-send-email-zhengsq-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2015-11-09 2:10 ` [PATCH v4 1/2] ASoC: codec: Inno codec driver for " Shunqian Zheng
2015-11-09 3:13 ` kbuild test robot [this message]
2015-11-09 3:13 ` [PATCH] ASoC: codec: fix platform_no_drv_owner.cocci warnings kbuild test robot
2015-11-09 2:10 ` [PATCH v4 2/2] ASoC: RK3036: Add binding doc of inno-rk3036 codec driver Shunqian Zheng
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=201511091100.MPMFFAtK%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=benchan@google.com \
--cc=benzh@chromium.org \
--cc=broonie@kernel.org \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kbuild-all@01.org \
--cc=kmixter@google.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.com \
--cc=zhengsq@rock-chips.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