From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: linux-next: Tree for Oct 5 (warnings: a. trace; b. mm/migrate)
Date: Tue, 5 Oct 2021 13:46:52 -0700 [thread overview]
Message-ID: <c1d9e328-ad7c-920b-6c24-9e1598a6421c@infradead.org> (raw)
In-Reply-To: <20211005190628.1f26b13d@canb.auug.org.au>
On 10/5/21 1:06 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20211001:
>
on x86_64:
a. randconfig: KCONFIG_SEED=0xBFBEA13C
../kernel/trace/trace.c:1712:13: error: 'trace_create_maxlat_file' defined but not used [-Werror=unused-function]
static void trace_create_maxlat_file(struct trace_array *tr,
b. randconfig: KCONFIG_SEED=0xFD1CE406
../mm/migrate.c:3216:22: error: 'migrate_on_reclaim_callback' defined but not used [-Werror=unused-function]
static int __meminit migrate_on_reclaim_callback(struct notifier_block *self,
^~~~~~~~~~~~~~~~~~~~~~~~~~~
../mm/migrate.c:3197:13: error: 'set_migration_target_nodes' defined but not used [-Werror=unused-function]
static void set_migration_target_nodes(void)
^~~~~~~~~~~~~~~~~~~~~~~~~~
(example usage to get the randconfig files:
KCONFIG_SEED=0xBFBEA13C make [ARCH=x86_64] randconfig
)
--
~Randy
next prev parent reply other threads:[~2021-10-05 20:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 8:06 linux-next: Tree for Oct 5 Stephen Rothwell
2021-10-05 20:46 ` Randy Dunlap [this message]
2021-10-06 14:52 ` linux-next: Tree for Oct 5 (warnings: a. trace; b. mm/migrate) Dave Hansen
2021-10-06 14:56 ` Steven Rostedt
2021-10-06 16:39 ` Randy Dunlap
2021-10-06 18:16 ` Dave Hansen
2021-10-06 16:33 ` Randy Dunlap
2021-10-06 21:22 ` Steven Rostedt
2021-10-06 21:32 ` Randy Dunlap
2021-10-06 22:06 ` Steven Rostedt
2021-10-07 1:10 ` Steven Rostedt
2021-10-07 3:13 ` 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=c1d9e328-ad7c-920b-6c24-9e1598a6421c@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=rostedt@goodmis.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).