From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Cezary Rojewski <cezary.rojewski@intel.com>,
Jie Yang <yang.jie@linux.intel.com>,
moderated for non-subscribers <alsa-devel@alsa-project.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>
Subject: Re: linux-next: Tree for Oct 6 (sound/soc/intel/catpt/device.c)
Date: Tue, 6 Oct 2020 11:54:44 -0700 [thread overview]
Message-ID: <0d1072b7-c57c-6a50-0561-389ad6a3e414@infradead.org> (raw)
In-Reply-To: <20201006231234.701591b5@canb.auug.org.au>
On 10/6/20 5:12 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20201002:
>
on x86_64 or i386:
when CONFIG_MODULES is not set/enabled:
../sound/soc/intel/catpt/device.c: In function ‘catpt_resume’:
../sound/soc/intel/catpt/device.c:84:7: error: implicit declaration of function ‘module_is_live’; did you mean ‘module_driver’? [-Werror=implicit-function-declaration]
if (!module_is_live(dev->driver->owner)) {
^~~~~~~~~~~~~~
module_driver
You could see
commit cdb685cb9158fa67f6f4584ea39279ed7ae39253
Author: Danil Kipnis <danil.kipnis@cloud.ionos.com>
Date: Thu May 21 20:59:09 2020 +0200
RDMA/rnbd: Fix compilation error when CONFIG_MODULES is disabled
for a possible fix.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
next parent reply other threads:[~2020-10-06 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201006231234.701591b5@canb.auug.org.au>
2020-10-06 18:54 ` Randy Dunlap [this message]
2020-10-06 19:35 ` linux-next: Tree for Oct 6 (sound/soc/intel/catpt/device.c) Randy Dunlap
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=0d1072b7-c57c-6a50-0561-389ad6a3e414@infradead.org \
--to=rdunlap@infradead.org \
--cc=alsa-devel@alsa-project.org \
--cc=cezary.rojewski@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=sfr@canb.auug.org.au \
--cc=yang.jie@linux.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;
as well as URLs for NNTP newsgroup(s).