mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: codekipper@gmail.com
Cc: kbuild-all@01.org, maxime.ripard@free-electrons.com,
	lgirdwood@gmail.com, linux-arm-kernel@lists.infradead.org,
	broonie@kernel.org, linux-sunxi@googlegroups.com,
	linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
	be17068@iperbole.bo.it, Marcus Cooper <codekipper@gmail.com>
Subject: Re: [PATCH v2 4/4] ASOC: sunxi: Add support for the spdif block
Date: Thu, 1 Oct 2015 02:52:46 +0800	[thread overview]
Message-ID: <201510010231.FvvWaROC%fengguang.wu@intel.com> (raw)
In-Reply-To: <1443635458-8873-5-git-send-email-codekipper@gmail.com>

Hi Marcus,

[auto build test results on next-20150930 -- if it's inappropriate base, please ignore]

reproduce:
  # apt-get install sparse
  make ARCH=x86_64 allmodconfig
  make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> sound/soc/sunxi/sun4i-spdif.c:207:6: sparse: symbol 'sun4i_snd_txctrl_on' was not declared. Should it be static?
>> sound/soc/sunxi/sun4i-spdif.c:231:6: sparse: symbol 'sun4i_snd_txctrl_off' was not declared. Should it be static?
>> sound/soc/sunxi/sun4i-spdif.c:451:28: sparse: incorrect type in initializer (different base types)
   sound/soc/sunxi/sun4i-spdif.c:451:28:    expected unsigned long long [unsigned] [usertype] formats
   sound/soc/sunxi/sun4i-spdif.c:451:28:    got restricted snd_pcm_format_t

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

  parent reply	other threads:[~2015-09-30 18:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30 17:50 [PATCH v2 0/4] Add SPDIF support for Allwinner SoCs codekipper
2015-09-30 17:50 ` [PATCH v2 1/4] dt-bindings: add sunxi SPDIF transceiver bindings codekipper
2015-10-01 20:12   ` Maxime Ripard
2015-10-02  5:24     ` Code Kipper
2015-10-05  8:41       ` Maxime Ripard
2015-10-05 10:40         ` Code Kipper
2015-09-30 17:50 ` [PATCH v2 2/4] dt-binding: Add sunxi S/PDIF machine driver codekipper
2015-09-30 17:50 ` [PATCH v2 3/4] ASoC: sunxi: Add " codekipper
2015-09-30 17:50 ` [PATCH v2 4/4] ASOC: sunxi: Add support for the spdif block codekipper
2015-09-30 18:26   ` [PATCH] ASOC: sunxi: fix platform_no_drv_owner.cocci warnings kbuild test robot
2015-09-30 18:26   ` [PATCH v2 4/4] ASOC: sunxi: Add support for the spdif block kbuild test robot
2015-09-30 18:52   ` kbuild test robot [this message]
2015-09-30 18:52   ` [RFC PATCH] ASOC: sunxi: sun4i_snd_txctrl_on() can be static kbuild test robot
2015-10-01 20:11   ` [PATCH v2 4/4] ASOC: sunxi: Add support for the spdif block Maxime Ripard
2015-10-02  6:44     ` Code Kipper
2015-10-06  9:00       ` Maxime Ripard
2015-10-06 10:38         ` Code Kipper
2015-10-26 19:20           ` Maxime Ripard

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=201510010231.FvvWaROC%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=be17068@iperbole.bo.it \
    --cc=broonie@kernel.org \
    --cc=codekipper@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=maxime.ripard@free-electrons.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

Powered by JetHome