From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Zhen Ni <nizhen@uniontech.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"keescook@chromium.org" <keescook@chromium.org>,
"mcgrof@kernel.org" <mcgrof@kernel.org>,
"vincent.guittot@linaro.org" <vincent.guittot@linaro.org>,
"juri.lelli@redhat.com" <juri.lelli@redhat.com>
Subject: Re: [PATCH 0/8] sched: Move a series of sysctls starting with sys/kernel/sched_*
Date: Tue, 15 Feb 2022 06:01:34 +0000 [thread overview]
Message-ID: <625e6989-dcd9-9dab-8c15-8f15321f10a2@nvidia.com> (raw)
In-Reply-To: <20220215052214.5286-1-nizhen@uniontech.com>
On 2/14/22 21:22, Zhen Ni wrote:
> *** BLURB HERE ***
>
empty Cover-letter ?
-ck
prev parent reply other threads:[~2022-02-15 6:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 5:22 Zhen Ni
2022-02-15 5:22 ` [PATCH 1/8] sched: Move child_runs_first sysctls to fair.c Zhen Ni
2022-02-15 5:22 ` [PATCH 2/8] sched: Move schedstats sysctls to core.c Zhen Ni
2022-02-15 5:22 ` [PATCH 3/8] sched: Move rt_period/runtime sysctls to rt.c Zhen Ni
2022-02-15 7:47 ` kernel test robot
2022-02-15 7:53 ` Luis Chamberlain
2022-02-15 11:23 ` kernel test robot
2022-02-15 5:22 ` [PATCH 4/8] sched: Move deadline_period sysctls to deadline.c Zhen Ni
2022-02-15 5:22 ` [PATCH 5/8] sched: Move rr_timeslice sysctls to rt.c Zhen Ni
2022-02-15 5:22 ` [PATCH 6/8] sched: Move uclamp_util sysctls to core.c Zhen Ni
2022-02-15 5:22 ` [PATCH 7/8] sched: Move cfs_bandwidth_slice sysctls to fair.c Zhen Ni
2022-02-15 5:22 ` [PATCH 8/8] sched: Move energy_aware sysctls to topology.c Zhen Ni
2022-02-15 6:01 ` Chaitanya Kulkarni [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=625e6989-dcd9-9dab-8c15-8f15321f10a2@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=juri.lelli@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mingo@redhat.com \
--cc=nizhen@uniontech.com \
--cc=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®