All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juerg Haefliger <juerg.haefliger@canonical.com>
To: linux@armlinux.org.uk, linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, Juerg Haefliger <juergh@canonical.com>
Subject: [PATCH 3/3] ARM: Kconfig.debug: Fix indentation
Date: Tue, 17 May 2022 16:14:24 +0200	[thread overview]
Message-ID: <20220517141424.331759-4-juergh@canonical.com> (raw)
In-Reply-To: <20220517141424.331759-1-juergh@canonical.com>

The convention for indentation seems to be a single tab. Help text is
further indented by an additional two whitespaces. Fix the lines that
violate these rules.

Signed-off-by: Juerg Haefliger <juergh@canonical.com>
---
 arch/arm/Kconfig.debug | 35 +++++++++++++++++------------------
 1 file changed, 17 insertions(+), 18 deletions(-)

diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug
index 0c9497d549e3..4b00b1fd9ab3 100644
--- a/arch/arm/Kconfig.debug
+++ b/arch/arm/Kconfig.debug
@@ -22,28 +22,28 @@ config DEBUG_WX
 	depends on MMU
 	select ARM_PTDUMP_CORE
 	help
-		Generate a warning if any W+X mappings are found at boot.
+	  Generate a warning if any W+X mappings are found at boot.
 
-		This is useful for discovering cases where the kernel is leaving
-		W+X mappings after applying NX, as such mappings are a security risk.
+	  This is useful for discovering cases where the kernel is leaving
+	  W+X mappings after applying NX, as such mappings are a security risk.
 
-		Look for a message in dmesg output like this:
+	  Look for a message in dmesg output like this:
 
-			arm/mm: Checked W+X mappings: passed, no W+X pages found.
+		arm/mm: Checked W+X mappings: passed, no W+X pages found.
 
-		or like this, if the check failed:
+	  or like this, if the check failed:
 
-			arm/mm: Checked W+X mappings: FAILED, <N> W+X pages found.
+		arm/mm: Checked W+X mappings: FAILED, <N> W+X pages found.
 
-		Note that even if the check fails, your kernel is possibly
-		still fine, as W+X mappings are not a security hole in
-		themselves, what they do is that they make the exploitation
-		of other unfixed kernel bugs easier.
+	  Note that even if the check fails, your kernel is possibly
+	  still fine, as W+X mappings are not a security hole in
+	  themselves, what they do is that they make the exploitation
+	  of other unfixed kernel bugs easier.
 
-		There is no runtime or memory usage effect of this option
-		once the kernel has booted up - it's a one time check.
+	  There is no runtime or memory usage effect of this option
+	  once the kernel has booted up - it's a one time check.
 
-		If in doubt, say "Y".
+	  If in doubt, say "Y".
 
 choice
 	prompt "Choose kernel unwinder"
@@ -293,7 +293,7 @@ choice
 		select DEBUG_UART_8250
 		help
 		  Say Y here if you want the debug print routines to direct
-                  their output to the CNS3xxx UART0.
+		  their output to the CNS3xxx UART0.
 
 	config DEBUG_DAVINCI_DA8XX_UART1
 		bool "Kernel low-level debugging on DaVinci DA8XX using UART1"
@@ -847,7 +847,7 @@ choice
 		select DEBUG_UART_8250
 		help
 		  Say Y here if you want kernel low-level debugging support
-                  on Rockchip RV1108 based platforms.
+		  on Rockchip RV1108 based platforms.
 
 	config DEBUG_RV1108_UART1
 		bool "Kernel low-level debugging messages via Rockchip RV1108 UART1"
@@ -1724,7 +1724,7 @@ config DEBUG_UART_PHYS
 	default 0xffffee00 if DEBUG_AT91_SAM9263_DBGU
 	default 0xfffff200 if DEBUG_AT91_RM9200_DBGU
 	depends on ARCH_EP93XX || \
-	        DEBUG_LL_UART_8250 || DEBUG_LL_UART_PL01X || \
+		DEBUG_LL_UART_8250 || DEBUG_LL_UART_PL01X || \
 		DEBUG_UART_8250 || DEBUG_UART_PL01X || DEBUG_MESON_UARTAO || \
 		DEBUG_QCOM_UARTDM || DEBUG_R7S72100_SCIF2 || \
 		DEBUG_R7S9210_SCIF2 || DEBUG_R7S9210_SCIF4 || \
@@ -1895,7 +1895,6 @@ config DEBUG_UNCOMPRESS
 	  When this option is set, the selected DEBUG_LL output method
 	  will be re-used for normal decompressor output on multiplatform
 	  kernels.
-	  
 
 config UNCOMPRESS_INCLUDE
 	string
-- 
2.32.0


WARNING: multiple messages have this Message-ID (diff)
From: Juerg Haefliger <juerg.haefliger@canonical.com>
To: linux@armlinux.org.uk, linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, Juerg Haefliger <juergh@canonical.com>
Subject: [PATCH 3/3] ARM: Kconfig.debug: Fix indentation
Date: Tue, 17 May 2022 16:14:24 +0200	[thread overview]
Message-ID: <20220517141424.331759-4-juergh@canonical.com> (raw)
In-Reply-To: <20220517141424.331759-1-juergh@canonical.com>

The convention for indentation seems to be a single tab. Help text is
further indented by an additional two whitespaces. Fix the lines that
violate these rules.

Signed-off-by: Juerg Haefliger <juergh@canonical.com>
---
 arch/arm/Kconfig.debug | 35 +++++++++++++++++------------------
 1 file changed, 17 insertions(+), 18 deletions(-)

diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug
index 0c9497d549e3..4b00b1fd9ab3 100644
--- a/arch/arm/Kconfig.debug
+++ b/arch/arm/Kconfig.debug
@@ -22,28 +22,28 @@ config DEBUG_WX
 	depends on MMU
 	select ARM_PTDUMP_CORE
 	help
-		Generate a warning if any W+X mappings are found at boot.
+	  Generate a warning if any W+X mappings are found at boot.
 
-		This is useful for discovering cases where the kernel is leaving
-		W+X mappings after applying NX, as such mappings are a security risk.
+	  This is useful for discovering cases where the kernel is leaving
+	  W+X mappings after applying NX, as such mappings are a security risk.
 
-		Look for a message in dmesg output like this:
+	  Look for a message in dmesg output like this:
 
-			arm/mm: Checked W+X mappings: passed, no W+X pages found.
+		arm/mm: Checked W+X mappings: passed, no W+X pages found.
 
-		or like this, if the check failed:
+	  or like this, if the check failed:
 
-			arm/mm: Checked W+X mappings: FAILED, <N> W+X pages found.
+		arm/mm: Checked W+X mappings: FAILED, <N> W+X pages found.
 
-		Note that even if the check fails, your kernel is possibly
-		still fine, as W+X mappings are not a security hole in
-		themselves, what they do is that they make the exploitation
-		of other unfixed kernel bugs easier.
+	  Note that even if the check fails, your kernel is possibly
+	  still fine, as W+X mappings are not a security hole in
+	  themselves, what they do is that they make the exploitation
+	  of other unfixed kernel bugs easier.
 
-		There is no runtime or memory usage effect of this option
-		once the kernel has booted up - it's a one time check.
+	  There is no runtime or memory usage effect of this option
+	  once the kernel has booted up - it's a one time check.
 
-		If in doubt, say "Y".
+	  If in doubt, say "Y".
 
 choice
 	prompt "Choose kernel unwinder"
@@ -293,7 +293,7 @@ choice
 		select DEBUG_UART_8250
 		help
 		  Say Y here if you want the debug print routines to direct
-                  their output to the CNS3xxx UART0.
+		  their output to the CNS3xxx UART0.
 
 	config DEBUG_DAVINCI_DA8XX_UART1
 		bool "Kernel low-level debugging on DaVinci DA8XX using UART1"
@@ -847,7 +847,7 @@ choice
 		select DEBUG_UART_8250
 		help
 		  Say Y here if you want kernel low-level debugging support
-                  on Rockchip RV1108 based platforms.
+		  on Rockchip RV1108 based platforms.
 
 	config DEBUG_RV1108_UART1
 		bool "Kernel low-level debugging messages via Rockchip RV1108 UART1"
@@ -1724,7 +1724,7 @@ config DEBUG_UART_PHYS
 	default 0xffffee00 if DEBUG_AT91_SAM9263_DBGU
 	default 0xfffff200 if DEBUG_AT91_RM9200_DBGU
 	depends on ARCH_EP93XX || \
-	        DEBUG_LL_UART_8250 || DEBUG_LL_UART_PL01X || \
+		DEBUG_LL_UART_8250 || DEBUG_LL_UART_PL01X || \
 		DEBUG_UART_8250 || DEBUG_UART_PL01X || DEBUG_MESON_UARTAO || \
 		DEBUG_QCOM_UARTDM || DEBUG_R7S72100_SCIF2 || \
 		DEBUG_R7S9210_SCIF2 || DEBUG_R7S9210_SCIF4 || \
@@ -1895,7 +1895,6 @@ config DEBUG_UNCOMPRESS
 	  When this option is set, the selected DEBUG_LL output method
 	  will be re-used for normal decompressor output on multiplatform
 	  kernels.
-	  
 
 config UNCOMPRESS_INCLUDE
 	string
-- 
2.32.0


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-05-17 14:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 14:14 [PATCH 0/3] ARM: Kconfig: Style cleanups Juerg Haefliger
2022-05-17 14:14 ` Juerg Haefliger
2022-05-17 14:14 ` [PATCH 1/3] ARM: Kconfig: Fix indentation and add comments Juerg Haefliger
2022-05-17 14:14   ` Juerg Haefliger
2022-05-17 14:33   ` Russell King (Oracle)
2022-05-17 14:33     ` Russell King (Oracle)
2022-05-18  6:43     ` [PATCH v2 1/3] ARM: Kconfig: Fix indentation Juerg Haefliger
2022-05-18  6:43       ` Juerg Haefliger
2022-05-17 14:14 ` [PATCH 2/3] ARM: Kconfig-nommu: Fix indentation and quotes Juerg Haefliger
2022-05-17 14:14   ` Juerg Haefliger
2022-05-17 14:14 ` Juerg Haefliger [this message]
2022-05-17 14:14   ` [PATCH 3/3] ARM: Kconfig.debug: Fix indentation Juerg Haefliger

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=20220517141424.331759-4-juergh@canonical.com \
    --to=juerg.haefliger@canonical.com \
    --cc=juergh@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.