From: Christopher Diaz Riveros <chrisadr@gentoo.org>
To: juri.lelli@gmail.com, peterz@infradead.org, mingo@redhat.com
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: [RFC] sched/headers: comments clean up <linux/sched.h>
Date: Wed, 21 Feb 2018 11:56:46 -0500 [thread overview]
Message-ID: <20180221165646.15432-1-chrisadr@gentoo.org> (raw)
In-Reply-To: <1518787521.2464.20.camel@gentoo.org>
Remove inline comments to merge them into comment blocks.
Enhance readability from source code by giving descriptions from the
structures and data in comment blocks instead from inline comments.
Signed-off-by: Christopher Diaz Riveros <chrisadr@gentoo.org>
---
include/linux/sched.h | 15 ++++++++++++---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/include/linux/sched.h b/include/linux/sched.h
index b161ef8a902e..693a6e51ed0c 100644
--- a/include/linux/sched.h
+++ b/include/linux/sched.h
@@ -221,12 +221,21 @@ struct task_cputime {
#define prof_exp stime
#define sched_exp sum_exec_runtime
+/*
+ * vtime_state states:
+ *
+ * @VTIME_INACTIVE tells if task is sleeping or running in a CPU with
+ * VTIME inactive.
+ *
+ * @VTIME_USER tells if task is running in userspace in a CPU with
+ * VTIME active.
+ *
+ * @VTIME_SYS tells if task is running in kernelspace in a CPU with
+ * VTIME active.
+ */
enum vtime_state {
- /* Task is sleeping or running in a CPU with VTIME inactive: */
VTIME_INACTIVE = 0,
- /* Task runs in userspace in a CPU with VTIME active: */
VTIME_USER,
- /* Task runs in kernelspace in a CPU with VTIME active: */
VTIME_SYS,
};
--
2.16.2
next prev parent reply other threads:[~2018-02-21 16:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 15:43 [PATCH-next] sched/headers: Clean up <linux/sched.h> Christopher Diaz Riveros
2018-02-15 16:52 ` Peter Zijlstra
2018-02-15 17:10 ` Christopher Díaz Riveros
2018-02-16 9:44 ` Juri Lelli
2018-02-16 13:25 ` Christopher Díaz Riveros
2018-02-21 8:09 ` Juri Lelli
2018-02-21 16:56 ` Christopher Diaz Riveros [this message]
2018-02-15 17:49 ` Randy Dunlap
2018-02-15 18:10 ` Christopher Díaz Riveros
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=20180221165646.15432-1-chrisadr@gentoo.org \
--to=chrisadr@gentoo.org \
--cc=juri.lelli@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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).