From: kbuild test robot <lkp@intel.com>
To: Bhumika Goyal <bhumirks@gmail.com>
Cc: kbuild-all@01.org, julia.lawall@lip6.fr, perex@perex.cz,
tiwai@suse.com, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, Bhumika Goyal <bhumirks@gmail.com>
Subject: Re: [PATCH] sound: pci: cs46xx: constify snd_pcm_ops structures
Date: Fri, 27 Jan 2017 00:48:39 +0800 [thread overview]
Message-ID: <201701270048.pCBPfvhB%fengguang.wu@intel.com> (raw)
In-Reply-To: <1485442409-2962-1-git-send-email-bhumirks@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2445 bytes --]
Hi Bhumika,
[auto build test ERROR on sound/for-next]
[also build test ERROR on v4.10-rc5 next-20170125]
[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/Bhumika-Goyal/sound-pci-cs46xx-constify-snd_pcm_ops-structures/20170126-230341
base: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git for-next
config: x86_64-rhel (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
Note: the linux-review/Bhumika-Goyal/sound-pci-cs46xx-constify-snd_pcm_ops-structures/20170126-230341 HEAD 59da8ce3cc92652020c8c6a3ad0a4b11d8ee5a48 builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
>> sound/pci/cs46xx/cs46xx_lib.c:1657:27: error: conflicting type qualifiers for 'snd_cs46xx_playback_rear_ops'
static struct snd_pcm_ops snd_cs46xx_playback_rear_ops = {
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
sound/pci/cs46xx/cs46xx_lib.c:75:33: note: previous declaration of 'snd_cs46xx_playback_rear_ops' was here
static const struct snd_pcm_ops snd_cs46xx_playback_rear_ops;
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/snd_cs46xx_playback_rear_ops +1657 sound/pci/cs46xx/cs46xx_lib.c
^1da177e Linus Torvalds 2005-04-16 1651 chip->active_ctrl(chip, -1);
^1da177e Linus Torvalds 2005-04-16 1652
^1da177e Linus Torvalds 2005-04-16 1653 return 0;
^1da177e Linus Torvalds 2005-04-16 1654 }
^1da177e Linus Torvalds 2005-04-16 1655
^1da177e Linus Torvalds 2005-04-16 1656 #ifdef CONFIG_SND_CS46XX_NEW_DSP
3d19f804 Takashi Iwai 2005-11-17 @1657 static struct snd_pcm_ops snd_cs46xx_playback_rear_ops = {
^1da177e Linus Torvalds 2005-04-16 1658 .open = snd_cs46xx_playback_open_rear,
^1da177e Linus Torvalds 2005-04-16 1659 .close = snd_cs46xx_playback_close,
^1da177e Linus Torvalds 2005-04-16 1660 .ioctl = snd_pcm_lib_ioctl,
:::::: The code at line 1657 was first introduced by commit
:::::: 3d19f804ef5f1d15fe001fc8d1ed58fac9d591fb [ALSA] Remove xxx_t typedefs: PCI CS46xx
:::::: TO: Takashi Iwai <tiwai@suse.de>
:::::: CC: Jaroslav Kysela <perex@suse.cz>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 38270 bytes --]
prev parent reply other threads:[~2017-01-26 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 14:53 Bhumika Goyal
2017-01-26 15:09 ` Takashi Iwai
2017-01-26 16:48 ` kbuild test robot [this message]
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=201701270048.pCBPfvhB%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bhumirks@gmail.com \
--cc=julia.lawall@lip6.fr \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--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 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®