From: "Paul E. McKenney" <paulmck@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: broonie@kernel.org,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-um <linux-um@lists.infradead.org>
Subject: Re: linux-next: Tree for Sep 27 (uml 64-bit or 32-bit: tinyconfig)
Date: Tue, 27 Sep 2022 14:28:21 -0700 [thread overview]
Message-ID: <20220927212821.GX4196@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <f1b22431-074d-32f1-b67a-34c51e4d072a@infradead.org>
On Tue, Sep 27, 2022 at 02:13:29PM -0700, Randy Dunlap wrote:
>
>
> On 9/27/22 13:10, broonie@kernel.org wrote:
> > Hi all,
> >
> > Changes since 20220923:
> >
>
> In file included from ../include/linux/notifier.h:16,
> from ../include/linux/memory_hotplug.h:7,
> from ../include/linux/mmzone.h:1244,
> from ../include/linux/gfp.h:7,
> from ../include/linux/slab.h:15,
> from ../include/linux/crypto.h:20,
> from ../arch/x86/um/shared/sysdep/kernel-offsets.h:5,
> from ../arch/um/kernel/asm-offsets.c:1:
> ../include/linux/srcu.h: In function ‘srcu_read_lock_nmisafe’:
> ../include/linux/srcu.h:181:26: error: implicit declaration of function ‘__srcu_read_lock_nmisafe’; did you mean ‘srcu_read_lock_nmisafe’? [-Werror=implicit-function-declaration]
> 181 | retval = __srcu_read_lock_nmisafe(ssp, true);
> | ^~~~~~~~~~~~~~~~~~~~~~~~
> | srcu_read_lock_nmisafe
> ../include/linux/srcu.h: In function ‘srcu_read_unlock_nmisafe’:
> ../include/linux/srcu.h:226:17: error: implicit declaration of function ‘__srcu_read_unlock_nmisafe’; did you mean ‘srcu_read_unlock_nmisafe’? [-Werror=implicit-function-declaration]
> 226 | __srcu_read_unlock_nmisafe(ssp, idx, true);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> | srcu_read_unlock_nmisafe
Could you please send your .config or tell me how you generated it?
Thanx, Paul
next prev parent reply other threads:[~2022-09-27 21:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 20:10 linux-next: Tree for Sep 27 broonie
2022-09-27 21:13 ` linux-next: Tree for Sep 27 (uml 64-bit or 32-bit: tinyconfig) Randy Dunlap
2022-09-27 21:28 ` Paul E. McKenney [this message]
2022-09-27 21:33 ` Randy Dunlap
2022-09-27 22:42 ` Paul E. McKenney
2022-09-28 3:27 ` Randy Dunlap
2022-09-28 6:25 ` Paul E. McKenney
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=20220927212821.GX4196@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).