mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Jun Nie <jun.nie@linaro.org>
Cc: kbuild-all@01.org, Mark Brown <broonie@kernel.org>,
	alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
	linux-kernel@vger.kernel.org
Subject: [asoc:topic/zx 2/4] sound/soc/zte/zx296702-i2s.c:358:27: sparse: symbol 'zx_i2s_dai' was not declared. Should it be static?
Date: Thu, 4 Jun 2015 21:00:50 +0800	[thread overview]
Message-ID: <201506042120.M9liQXGN%fengguang.wu@intel.com> (raw)

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git topic/zx
head:   dc772a4cf76113d7269e4fb1c45e5d85c0cf458e
commit: e5d4cd87800ce12c356e7eb571e565e839ab3a90 [2/4] ASoC: zx: Add ZTE zx296702 I2S DAI driver
reproduce:
  # apt-get install sparse
  git checkout e5d4cd87800ce12c356e7eb571e565e839ab3a90
  make ARCH=x86_64 allmodconfig
  make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> sound/soc/zte/zx296702-i2s.c:358:27: sparse: symbol 'zx_i2s_dai' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild                 Intel Corporation

             reply	other threads:[~2015-06-04 13:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 13:00 kbuild test robot [this message]
2015-06-04 13:00 ` [PATCH asoc] ASoC: zx: zx_i2s_dai can be static kbuild test robot
2015-06-04 14:39   ` 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=201506042120.M9liQXGN%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=jun.nie@linaro.org \
    --cc=kbuild-all@01.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.de \
    /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®