[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20201115195734.8338-2-matheus@castello.eng.br>
Date: Sun, 15 Nov 2020 16:57:29 -0300
From: Matheus Castello <matheus@...tello.eng.br>
To: kys@...rosoft.com, haiyangz@...rosoft.com, sthemmin@...rosoft.com,
wei.liu@...nel.org
Cc: sashal@...nel.org, Tianyu.Lan@...rosoft.com, decui@...rosoft.com,
mikelley@...rosoft.com, sunilmut@...rosoft.com,
linux-hyperv@...r.kernel.org, linux-kernel@...r.kernel.org,
Matheus Castello <matheus@...tello.eng.br>
Subject: [PATCH 1/6] drivers: hv: Fix hyperv_record_panic_msg path on comment
Fix the kernel parameter path in the comment, in the documentation the
parameter is correct but if someone who is studying the code and see
this first can get confused and try to access the wrong path/parameter
Signed-off-by: Matheus Castello <matheus@...tello.eng.br>
---
drivers/hv/vmbus_drv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
index 4fad3e6745e5..9ed7e3b1d654 100644
--- a/drivers/hv/vmbus_drv.c
+++ b/drivers/hv/vmbus_drv.c
@@ -55,7 +55,7 @@ int vmbus_interrupt;
/*
* Boolean to control whether to report panic messages over Hyper-V.
*
- * It can be set via /proc/sys/kernel/hyperv/record_panic_msg
+ * It can be set via /proc/sys/kernel/hyperv_record_panic_msg
*/
static int sysctl_record_panic_msg = 1;
--
2.28.0
Powered by blists - more mailing lists