From: Chen Zhongjin <chenzhongjin@huawei.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the sound-asoc-fixes tree
Date: Mon, 7 Nov 2022 11:03:39 +0800 [thread overview]
Message-ID: <94003e66-399f-2c13-0ad5-72d5c6e87da3@huawei.com> (raw)
In-Reply-To: <20221107084318.5a83394a@canb.auug.org.au>
Hi,
On 2022/11/7 5:43, Stephen Rothwell wrote:
> Hi Stephen,
>
> On Mon, 31 Oct 2022 08:39:17 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> Hi all,
>>
>> After merging the sound-asoc-fixes tree, today's linux-next build (arm
>> multi_v7_defconfig) produced this warning:
>>
>> WARNING: modpost: sound/soc/snd-soc-core.o: section mismatch in reference: init_module (section: .init.text) -> snd_soc_util_exit (section: .exit.text)
>>
>> Introduced by commit
>>
>> 6ec27c53886c ("ASoC: core: Fix use-after-free in snd_soc_exit()")
> I am still getting this warning.
I compiled linux-next/master and didn't find the warning.
Also I noticed that the fix patch 06ba770a799f ("ASoC: soc-utils: Remove
__exit for snd_soc_util_exit()") is on the tree.
Have no idea what's going wrong. Could you please check whether this
fixup takes effect?
next prev parent reply other threads:[~2022-11-07 3:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 21:39 Stephen Rothwell
2022-10-31 1:17 ` Chen Zhongjin
2022-11-06 21:43 ` Stephen Rothwell
2022-11-07 3:03 ` Chen Zhongjin [this message]
2022-11-07 3:52 ` Stephen Rothwell
2025-01-09 4:25 Stephen Rothwell
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=94003e66-399f-2c13-0ad5-72d5c6e87da3@huawei.com \
--to=chenzhongjin@huawei.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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®