All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: simon.ho.cnxt@gmail.com
Cc: alsa-devel@alsa-project.org, Simon Ho <simon.ho@conexant.com>,
	lgirdwood@gmail.com, tiwai@suse.com, broonie@kernel.org,
	kbuild-all@01.org
Subject: Re: [alsa_devel] [PATCH v3 2/2] ASoC: Add driver support fro Conexant CX2092X DSP
Date: Wed, 22 Feb 2017 01:44:01 +0800	[thread overview]
Message-ID: <201702220127.8Yf496qG%fengguang.wu@intel.com> (raw)
In-Reply-To: <4a4e60530c00c33f554b8157c2afa0a57362c0bc.1487684248.git.simon.ho@conexant.com>

Hi Simon,

[auto build test WARNING on asoc/for-next]
[also build test WARNING on v4.10 next-20170220]
[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/simon-ho-cnxt-gmail-com/ASoC-add-driver-support-for-Conexant-CX2092X-DSP/20170221-235253
base:   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next


coccinelle warnings: (new ones prefixed by >>)

>> sound/soc/codecs/cx2092x-i2c.c:43: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

  reply	other threads:[~2017-02-21 17:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21 13:58 [alsa_devel] [PATCH v3 0/2] ASoC: add driver support for Conexant CX2092X DSP simon.ho.cnxt
2017-02-21 13:58 ` [alsa_devel] [PATCH v3 1/2] doc: cx2092x: Add DT bingings doc for " simon.ho.cnxt
2017-02-21 13:58 ` [alsa_devel] [PATCH v3 2/2] ASoC: Add driver support fro Conexant " simon.ho.cnxt
2017-02-21 17:44   ` kbuild test robot [this message]
2017-02-21 17:44   ` [PATCH] ASoC: fix platform_no_drv_owner.cocci warnings kbuild test robot

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=201702220127.8Yf496qG%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=kbuild-all@01.org \
    --cc=lgirdwood@gmail.com \
    --cc=simon.ho.cnxt@gmail.com \
    --cc=simon.ho@conexant.com \
    --cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.