From: Luis Chamberlain <mcgrof@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>, peterz@infradead.org
Cc: Zhen Ni <nizhen@uniontech.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, keescook@chromium.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
tangmeng <tangmeng@uniontech.com>
Subject: Re: [PATCH v3 0/8] sched: Move a series of sysctls starting with sys/kernel/sched_*
Date: Fri, 18 Feb 2022 10:21:56 -0800 [thread overview]
Message-ID: <Yg/jxFqiuyR/xB2s@bombadil.infradead.org> (raw)
In-Reply-To: <20220217185238.802a7e2dd1980fee87be736c@linux-foundation.org>
On Thu, Feb 17, 2022 at 06:52:38PM -0800, Andrew Morton wrote:
> On Wed, 16 Feb 2022 23:51:08 -0800 Luis Chamberlain <mcgrof@kernel.org> wrote:
>
> > Are you folks OK if say Stephen adds a sysctl-next for linux-next so
> > we can beat on these there too?
>
> Sure. I just sent you a couple which I've collected.
OK thanks! I've merged those into sysctl-next [0]
Stephen,
Can you add it to the set of trees you pull? I'll send a patch to add
this to MAINTAINERS too then.
[0] git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git sysctl-next
Luis
next prev parent reply other threads:[~2022-02-18 18:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 11:45 [PATCH v3 0/8] sched: Move a series of sysctls starting with sys/kernel/sched_* Zhen Ni
2022-02-15 11:45 ` [PATCH v3 1/8] sched: Move child_runs_first sysctls to fair.c Zhen Ni
2022-02-15 11:45 ` [PATCH v3 2/8] sched: Move schedstats sysctls to core.c Zhen Ni
2022-02-15 11:45 ` [PATCH v3 3/8] sched: Move rt_period/runtime sysctls to rt.c Zhen Ni
2022-02-15 11:46 ` [PATCH v3 4/8] sched: Move deadline_period sysctls to deadline.c Zhen Ni
2022-02-15 11:46 ` [PATCH v3 5/8] sched: Move rr_timeslice sysctls to rt.c Zhen Ni
2022-02-15 11:46 ` [PATCH v3 6/8] sched: Move uclamp_util sysctls to core.c Zhen Ni
2022-02-15 11:46 ` [PATCH v3 7/8] sched: Move cfs_bandwidth_slice sysctls to fair.c Zhen Ni
2022-02-15 11:46 ` [PATCH v3 8/8] sched: Move energy_aware sysctls to topology.c Zhen Ni
2022-02-17 7:51 ` [PATCH v3 0/8] sched: Move a series of sysctls starting with sys/kernel/sched_* Luis Chamberlain
2022-02-18 2:52 ` Andrew Morton
2022-02-18 18:21 ` Luis Chamberlain [this message]
2022-02-20 0:05 ` Stephen Rothwell
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=Yg/jxFqiuyR/xB2s@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=juri.lelli@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nizhen@uniontech.com \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tangmeng@uniontech.com \
--cc=vincent.guittot@linaro.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).