From: Thomas Gleixner <tglx@linutronix.de>
To: tangmeng <tangmeng@uniontech.com>,
mcgrof@kernel.org, keescook@chromium.org, yzaikin@google.com,
john.stultz@linaro.org, sboyd@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
tangmeng <tangmeng@uniontech.com>
Subject: Re: [PATCH v4] kernel/time: move timer sysctls to its own file
Date: Mon, 31 Jan 2022 10:00:26 +0100 [thread overview]
Message-ID: <87pmo82sb9.ffs@tglx> (raw)
In-Reply-To: <20220131065728.6823-1-tangmeng@uniontech.com>
On Mon, Jan 31 2022 at 14:57, tangmeng@uniontech.com wrote:
> This moves the kernel/timer/timer.c respective sysctls to its own
> file.
Why? What's the reason and purpose of this? We are not moving code
around just because we can.
Thanks,
tglx
next prev parent reply other threads:[~2022-01-31 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 6:57 [PATCH v4] kernel/time: move timer sysctls to its own file tangmeng
2022-01-31 9:00 ` Thomas Gleixner [this message]
2022-01-31 9:53 ` kernel test robot
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=87pmo82sb9.ffs@tglx \
--to=tglx@linutronix.de \
--cc=john.stultz@linaro.org \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=sboyd@kernel.org \
--cc=tangmeng@uniontech.com \
--cc=yzaikin@google.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;
as well as URLs for NNTP newsgroup(s).