From: Randy Dunlap <rdunlap@infradead.org>
To: broonie@kernel.org, Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Zhen Ni <nizhen@uniontech.com>,
Luis Chamberlain <mcgrof@kernel.org>
Subject: Re: linux-next: Tree for Feb 24 (kernel/sched/core,rt)
Date: Thu, 24 Feb 2022 21:37:30 -0800 [thread overview]
Message-ID: <4d84840e-ed33-d7aa-58b2-86aecc3d7084@infradead.org> (raw)
In-Reply-To: <20220225021603.1960898-1-broonie@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]
On 2/24/22 18:16, broonie@kernel.org wrote:
> Hi all,
>
> Changes since 20220223:
>
> The btrfs tree gained several conflicts with the btrfs-fixes tree.
>
> The net-next tree gained conflicts with the net tree.
>
> The drm tree gained conflicts against the drm-fixes tree.
>
> The drm tree gained a conflict with the drm-intel-gt tree.
>
> The akpm tree was updated and merged, thanks to Andrew for his help with
> this.
>
> Non-merge commits (relative to Linus' tree): 7842
> 8121 files changed, 894334 insertions(+), 225439 deletions(-)
>
> ----------------------------------------------------------------------------
on x86_64 or i386:
../kernel/sched/core.c:1719:12: error: ‘sysctl_sched_uclamp_handler’ defined but not used [-Werror=unused-function]
static int sysctl_sched_uclamp_handler(struct ctl_table *table, int write,
^~~~~~~~~~~~~~~~~~~~~~~~~~~
../kernel/sched/rt.c:3020:12: error: ‘sched_rr_handler’ defined but not used [-Werror=unused-function]
static int sched_rr_handler(struct ctl_table *table, int write, void *buffer,
^~~~~~~~~~~~~~~~
../kernel/sched/rt.c:2981:12: error: ‘sched_rt_handler’ defined but not used [-Werror=unused-function]
static int sched_rt_handler(struct ctl_table *table, int write, void *buffer,
^~~~~~~~~~~~~~~~
Full randconfig file is attached.
--
~Randy
[-- Attachment #2: config-r2343.gz --]
[-- Type: application/gzip, Size: 45200 bytes --]
prev parent reply other threads:[~2022-02-25 5:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 2:16 linux-next: Tree for Feb 24 broonie
2022-02-25 5:37 ` 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=4d84840e-ed33-d7aa-58b2-86aecc3d7084@infradead.org \
--to=rdunlap@infradead.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=nizhen@uniontech.com \
/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®