From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Matteo Croce <mcroce@redhat.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Luis Chamberlain <mcgrof@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: Tree for May 30 (firmware_loader)
Date: Fri, 31 May 2019 10:06:46 +1000 [thread overview]
Message-ID: <20190531100646.212b065f@canb.auug.org.au> (raw)
In-Reply-To: <28716a14-772d-bc82-5111-34cd38cfda54@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
Hi all,
On Thu, 30 May 2019 09:10:13 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
>
> on i386 or x86_64:
> when CONFIG_PROC_SYSCTL is not set/enabled:
>
> ld: drivers/base/firmware_loader/fallback_table.o:(.data+0x1c): undefined reference to `sysctl_vals'
> ld: drivers/base/firmware_loader/fallback_table.o:(.data+0x20): undefined reference to `sysctl_vals'
> ld: drivers/base/firmware_loader/fallback_table.o:(.data+0x40): undefined reference to `sysctl_vals'
> ld: drivers/base/firmware_loader/fallback_table.o:(.data+0x44): undefined reference to `sysctl_vals'
Caused by commit
6a33853c5773 ("proc/sysctl: add shared variables for range check")
Added some more cc's
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-05-31 0:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 6:21 linux-next: Tree for May 30 Stephen Rothwell
2019-05-30 16:10 ` linux-next: Tree for May 30 (firmware_loader) Randy Dunlap
2019-05-31 0:06 ` Stephen Rothwell [this message]
2019-05-31 0:52 ` Matteo Croce
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=20190531100646.212b065f@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mcroce@redhat.com \
--cc=rdunlap@infradead.org \
/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®