From: Steven Rostedt <rostedt@goodmis.org>
To: Randy Dunlap <rdunlap@infradead.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>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: Tree for Oct 5 (warnings: a. trace; b. mm/migrate)
Date: Wed, 6 Oct 2021 18:06:51 -0400 [thread overview]
Message-ID: <20211006180651.73f46f11@gandalf.local.home> (raw)
In-Reply-To: <6d8f22a1-5f54-aa2a-7628-1d98a7f0fb95@infradead.org>
On Wed, 6 Oct 2021 14:32:21 -0700
Randy Dunlap <rdunlap@infradead.org> wrote:
> >> 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,
> >
> > Does this fix it?
> >
> > -- Steve
>
> Yes, thanks.
>
> Acked-by: Randy Dunlap <rdunlap@infradead.org> # build-tested
>
I believe the proper tags are:
Reported-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org> # build-tested
-- Steve
next prev parent reply other threads:[~2021-10-06 22:06 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 ` linux-next: Tree for Oct 5 (warnings: a. trace; b. mm/migrate) Randy Dunlap
2021-10-06 14:52 ` 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 [this message]
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=20211006180651.73f46f11@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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).