linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Nov 30 [drivers/base/firmware_loader/firmware_class.ko]
Date: Tue, 30 Nov 2021 08:09:07 -0800	[thread overview]
Message-ID: <11db050f-9728-8e0b-0081-6a2b943fccdf@infradead.org> (raw)
In-Reply-To: <YaZKkx6zXjG8FLL8@bombadil.infradead.org>

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



On 11/30/21 08:00, Luis Chamberlain wrote:
> On Tue, Nov 30, 2021 at 06:47:19AM -0800, Randy Dunlap wrote:
>>
>>
>> On 11/29/21 23:51, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20211129:
>>>
>>
>> on x86_64:
>> when CONFIG_FW_LOADER=m:
>>
>> ERROR: modpost: "unregister_firmware_config_sysctl" [drivers/base/firmware_loader/firmware_class.ko] undefined!
>> ERROR: modpost: "register_firmware_config_sysctl" [drivers/base/firmware_loader/firmware_class.ko] undefined!
>>
>>
>> Just export those 2 symbols, please.
> 
> Can you provide your .config because I cannot reproduce with
> CONFIG_FW_LOADER=m

Sure, it's attached.

-- 
~Randy

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

      reply	other threads:[~2021-11-30 16:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-30  7:51 linux-next: Tree for Nov 30 Stephen Rothwell
2021-11-30 14:47 ` linux-next: Tree for Nov 30 [drivers/base/firmware_loader/firmware_class.ko] Randy Dunlap
2021-11-30 16:00   ` Luis Chamberlain
2021-11-30 16:09     ` Randy Dunlap [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=11db050f-9728-8e0b-0081-6a2b943fccdf@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mcgrof@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;
as well as URLs for NNTP newsgroup(s).