From: kbuild test robot <lkp@intel.com>
To: Wei Yongjun <weiyj.lk@gmail.com>
Cc: kbuild-all@01.org, Bard Liao <bardliao@realtek.com>,
Oder Chiou <oder_chiou@realtek.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
Wei Yongjun <weiyongjun1@huawei.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] ASoC: rt5663: fix sparse warnings
Date: Sat, 17 Sep 2016 10:45:18 +0800 [thread overview]
Message-ID: <201609171011.E9z8MBt2%fengguang.wu@intel.com> (raw)
In-Reply-To: <1474076049-9416-1-git-send-email-weiyj.lk@gmail.com>
Hi Wei,
[auto build test WARNING on next-20160916]
url: https://github.com/0day-ci/linux/commits/Wei-Yongjun/ASoC-rt5663-fix-sparse-warnings/20160917-094530
coccinelle warnings: (new ones prefixed by >>)
>> sound/soc/codecs/rt5663.c:3203: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:[~2016-09-17 2:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-17 1:34 Wei Yongjun
2016-09-17 2:45 ` kbuild test robot [this message]
2016-09-17 2:45 ` [PATCH] ASoC: rt5663: fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-09-19 1:56 ` Bard Liao
2016-09-21 12:56 ` Applied "ASoC: rt5663: fix platform_no_drv_owner.cocci warnings" to the asoc tree Mark Brown
2016-09-21 12:56 ` Applied "ASoC: rt5663: fix sparse " Mark Brown
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=201609171011.E9z8MBt2%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--cc=kbuild-all@01.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=weiyj.lk@gmail.com \
--cc=weiyongjun1@huawei.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
all inboxes | Powered by JetHome®