From f75009fc1c1dfe0a37c29b61e04c501bb4f40539 Mon Sep 17 00:00:00 2001 From: Chia-Hao Chiu Date: Wed, 6 Aug 2025 19:05:58 +0800 Subject: [PATCH] examples/sleep: clarify /proc vs procfs wording Use "/proc" when the comment refers to the actual file (/proc/sleep) and keep "proc" when it denotes the procfs mechanism or related helper APIs. This makes the documentation consistent and avoids ambiguity between a file path and the proc filesystem itself. Signed-off-by: Chia-Hao Chiu --- examples/sleep.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/examples/sleep.c b/examples/sleep.c index ad46c9fb..60ad06e9 100644 --- a/examples/sleep.c +++ b/examples/sleep.c @@ -155,7 +155,7 @@ static int module_close(struct inode *inode, struct file *file) * functions. */ -/* File operations for our proc file. This is where we place pointers to all +/* File operations for our /proc file. This is where we place pointers to all * the functions called when somebody tries to do something to our file. NULL * means we don't want to deal with something. */ @@ -177,7 +177,7 @@ static const struct file_operations file_ops_4_our_proc_file = { }; #endif -/* Initialize the module - register the proc file */ +/* Initialize the module - register the /proc file */ static int __init sleep_init(void) { our_proc_file =