Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Vijendar Mukunda <Vijendar.Mukunda@amd.com>,
	broonie@kernel.org, alsa-devel@alsa-project.org
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	kbuild-all@lists.01.org, Takashi Iwai <tiwai@suse.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Vijendar Mukunda <Vijendar.Mukunda@amd.com>,
	Alexander.Deucher@amd.com, Virendra-Pratap.Arya@amd.com,
	Murali-krishna.Vemuri@amd.com
Subject: Re: [PATCH v3] ASoC: amd: add support for rt5682 codec in machine driver
Date: Tue, 16 Mar 2021 11:26:05 +0800	[thread overview]
Message-ID: <202103161110.6stib9Yp-lkp@intel.com> (raw)
In-Reply-To: <1615824133-21553-1-git-send-email-Vijendar.Mukunda@amd.com>

[-- Attachment #1: Type: text/plain, Size: 1644 bytes --]

Hi Vijendar,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on asoc/for-next]
[also build test ERROR on v5.12-rc3 next-20210315]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Vijendar-Mukunda/ASoC-amd-add-support-for-rt5682-codec-in-machine-driver/20210315-234723
base:   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://github.com/0day-ci/linux/commit/3ce3631a5e78f3564d42ce966b97b5496dec7db6
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Vijendar-Mukunda/ASoC-amd-add-support-for-rt5682-codec-in-machine-driver/20210315-234723
        git checkout 3ce3631a5e78f3564d42ce966b97b5496dec7db6
        # save the attached .config to linux build tree
        make W=1 ARCH=x86_64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   ld: sound/soc/amd/acp3x-rt5682-max9836.o: in function `soc_is_rltk_max':
>> acp3x-rt5682-max9836.c:(.text+0x840): multiple definition of `soc_is_rltk_max'; sound/soc/amd/acp-da7219-max98357a.o:acp-da7219-max98357a.c:(.text+0xd00): first defined here

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 65476 bytes --]

      parent reply	other threads:[~2021-03-16  3:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15 16:01 [PATCH v3] ASoC: amd: add support for rt5682 codec in machine driver Vijendar Mukunda
2021-03-15 16:00 ` Pierre-Louis Bossart
2021-03-16 13:37   ` Mukunda,Vijendar
2021-03-16 14:53     ` Pierre-Louis Bossart
2021-03-17  5:57       ` Shuming [范書銘]
2021-03-16  3:26 ` kernel 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=202103161110.6stib9Yp-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Murali-krishna.Vemuri@amd.com \
    --cc=Vijendar.Mukunda@amd.com \
    --cc=Virendra-Pratap.Arya@amd.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=lgirdwood@gmail.com \
    --cc=pierre-louis.bossart@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox