From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Pavel Machek <pavel@ucw.cz>, Len Brown <len.brown@intel.com>,
linux-pm@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Jani Nikula <jani.nikula@linux.intel.com>,
linux-doc@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH v5] kernel.h: add comments for enum system_states
Date: Sat, 6 Sep 2025 10:58:51 +0200 [thread overview]
Message-ID: <20250906105851.7c28416c@foz.lan> (raw)
In-Reply-To: <20250906052758.2767832-1-rdunlap@infradead.org>
Em Fri, 5 Sep 2025 22:27:58 -0700
Randy Dunlap <rdunlap@infradead.org> escreveu:
> Provide some basic comments about the system_states and what they imply.
> Also convert the comments to kernel-doc format.
>
> Split the enum declaration from the definition of the system_state
> variable so that kernel-doc notation works cleanly with it.
> This is picked up by Documentation/driver-api/basics.rst so it
> does not need further inclusion in the kernel docbooks.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Acked-by: Rafael J. Wysocki <rafael@kernel.org> # v1
> ---
> v2: add Rafael's Ack.
> v3: add Andrew
> v4: add DOC: so that this DOC: block can be used in Documentation/
> add Greg K-H
> add Jon Corbet, Mauro Chehab, & linux-doc
> v5: split enum declaration and definition (Jani Nikula)
> drop the DOC: block since it is no longer needed
>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: "Rafael J. Wysocki" <rafael@kernel.org>
> Cc: Pavel Machek <pavel@ucw.cz>
> Cc: Len Brown <len.brown@intel.com>
> Cc: linux-pm@vger.kernel.org
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Jani Nikula <jani.nikula@linux.intel.com>
> Cc: linux-doc@vger.kernel.org
> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
> Cc: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
> ---
> include/linux/kernel.h | 21 +++++++++++++++++----
> 1 file changed, 17 insertions(+), 4 deletions(-)
>
> --- linux-next-20250819.orig/include/linux/kernel.h
> +++ linux-next-20250819/include/linux/kernel.h
> @@ -164,11 +164,23 @@ extern int root_mountflags;
>
> extern bool early_boot_irqs_disabled;
>
> -/*
> - * Values used for system_state. Ordering of the states must not be changed
> +/**
> + * enum system_states - Values used for system_state.
> + *
> + * * @SYSTEM_BOOTING: %0, no init needed
> + * * @SYSTEM_SCHEDULING: system is ready for scheduling; OK to use RCU
> + * * @SYSTEM_FREEING_INITMEM: system is freeing all of initmem; almost running
> + * * @SYSTEM_RUNNING: system is up and running
> + * * @SYSTEM_HALT: system entered clean system halt state
> + * * @SYSTEM_POWER_OFF: system entered shutdown/clean power off state
> + * * @SYSTEM_RESTART: system entered emergency power off or normal restart
> + * * @SYSTEM_SUSPEND: system entered suspend or hibernate state
You forgot to drop the extra asterisk at the above. definitions.
Fixing it, feel free to add:
Reviewed-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> + *
> + * Note:
> + * Ordering of the states must not be changed
> * as code checks for <, <=, >, >= STATE.
> */
> -extern enum system_states {
> +enum system_states {
> SYSTEM_BOOTING,
> SYSTEM_SCHEDULING,
> SYSTEM_FREEING_INITMEM,
> @@ -177,7 +189,8 @@ extern enum system_states {
> SYSTEM_POWER_OFF,
> SYSTEM_RESTART,
> SYSTEM_SUSPEND,
> -} system_state;
> +};
> +extern enum system_states system_state;
>
> /*
> * General tracing related utility functions - trace_printk(),
Thanks,
Mauro
next prev parent reply other threads:[~2025-09-06 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-06 5:27 [PATCH v5] kernel.h: add comments for enum system_states Randy Dunlap
2025-09-06 8:58 ` Mauro Carvalho Chehab [this message]
2025-09-06 17:14 ` Randy Dunlap
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=20250906105851.7c28416c@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=jani.nikula@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=rdunlap@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