From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Shenghao Ding <shenghao-ding@ti.com>
Cc: tiwai@suse.de, broonie@kernel.org, 13564923607@139.com,
13916275206@139.com, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, baojun.xu@ti.com,
Baojun.Xu@fpt.com, jesse-ji@ti.com
Subject: Re: [PATCH v2] ALSA: hda/tas2781: Fix the ld issue reported by kernel test robot
Date: Mon, 12 May 2025 11:48:25 +0300 [thread overview]
Message-ID: <aCG12YmBS-9Vmc7N@smile.fi.intel.com> (raw)
In-Reply-To: <20250512081822.1513-1-shenghao-ding@ti.com>
On Mon, May 12, 2025 at 04:18:22PM +0800, Shenghao Ding wrote:
> After commit 9fa6a693ad8d ("ALSA: hda/tas2781: Remove tas2781_spi_fwlib.c
> and leverage SND_SOC_TAS2781_FMWLIB")created a separated lib for i2c,
> tasdevice_remove used for not only for I2C but for SPI being still in
> that lib caused ld issue.
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://urldefense.com/v3/__https://lore.kernel.org/
> | oe-kbuild-all/202505111855.FP2fScKA-lkp@intel.com/
> | __;!!G3vK!U-wdsvrOG1iezggZ55RYi8ikBxMaJDVs7u17Z9-7Xa-
> | 0lnyE4S3m2qmLCcHVK4qH1bD1JuBdzg$
This should be in a tag area below, each tag is exactly one line (the same way
as Fixes:, for example)
> All errors (new ones prefixed by >>):
> >> ld.lld: error: undefined symbol: tasdevice_remove
> >>> referenced by tas2781_hda.c:33 (sound/pci/hda/tas2781_hda.c:33)
> >>> vmlinux.o:(tas2781_hda_remove)
> To fix this issue, the implementation of tasdevice_remove was moved from
> tas2781-comlib-i2c.c to tas2781-comlib.c.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2025-05-15 8:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 8:18 [PATCH v2] ALSA: hda/tas2781: Fix the ld issue reported by kernel test robot Shenghao Ding
2025-05-12 8:48 ` Andy Shevchenko [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=aCG12YmBS-9Vmc7N@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=13564923607@139.com \
--cc=13916275206@139.com \
--cc=Baojun.Xu@fpt.com \
--cc=alsa-devel@alsa-project.org \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=jesse-ji@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shenghao-ding@ti.com \
--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 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.