From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: [broonie-sound:for-6.1 66/75] ERROR: modpost: "slim_stream_prepare" [sound/soc/codecs/snd-soc-wcd934x.ko] undefined!
Date: Thu, 1 Sep 2022 11:49:54 +0100 [thread overview]
Message-ID: <YxCOUjE9jTQQS98u@sirena.org.uk> (raw)
In-Reply-To: <039bf8da-5f20-4395-eb37-d60d4a358b0a@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 387 bytes --]
On Thu, Sep 01, 2022 at 12:53:24PM +0300, Krzysztof Kozlowski wrote:
> On 01/09/2022 11:02, kernel test robot wrote:
> >>> ERROR: modpost: "of_slim_get_device" [sound/soc/codecs/snd-soc-wcd934x.ko] undefined!
> I guess Mark that finally proves your point that these devices are too
> coupled for compile test.
> I can fix it up... or maybe just drop these two commits?
Either works.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-09-01 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 8:02 kernel test robot
2022-09-01 9:53 ` Krzysztof Kozlowski
2022-09-01 10:49 ` Mark Brown [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=YxCOUjE9jTQQS98u@sirena.org.uk \
--to=broonie@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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®