mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rong Tao <rtoax@foxmail.com>
To: rostedt@goodmis.org
Cc: Rong Tao <rtoax@foxmail.com>, Jan Kara <jack@suse.cz>,
	Heiko Carstens <hca@linux.ibm.com>,
	Gabriel Krisman Bertazi <krisman@collabora.com>,
	Amir Goldstein <amir73il@gmail.com>,
	Mike Leach <mike.leach@linaro.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	linux-kernel@vger.kernel.org (open list)
Subject: [PATCH] samples/Kconfig: fix up indentation
Date: Tue, 27 Sep 2022 21:52:07 +0800	[thread overview]
Message-ID: <tencent_BAA30488EB06A842C1595097BA2A7FAF9908@qq.com> (raw)

Fix up indentation before we get complaints from tooling.

Signed-off-by: Rong Tao <rtoax@foxmail.com>
---
 samples/Kconfig | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/samples/Kconfig b/samples/Kconfig
index 470ee3baf2e1..2605582d4e8f 100644
--- a/samples/Kconfig
+++ b/samples/Kconfig
@@ -23,7 +23,7 @@ config SAMPLE_TRACE_CUSTOM_EVENTS
 	  This builds the custom trace event example module.
 
 config SAMPLE_TRACE_PRINTK
-        tristate "Build trace_printk module - tests various trace_printk formats"
+	tristate "Build trace_printk module - tests various trace_printk formats"
 	depends on EVENT_TRACING && m
 	help
 	 This builds a module that calls trace_printk() and can be used to
@@ -47,7 +47,7 @@ config SAMPLE_FTRACE_DIRECT_MULTI
 	  the function addresses.
 
 config SAMPLE_TRACE_ARRAY
-        tristate "Build sample module for kernel access to Ftrace instancess"
+	tristate "Build sample module for kernel access to Ftrace instancess"
 	depends on EVENT_TRACING && m
 	help
 	 This builds a module that demonstrates the use of various APIs to
-- 
2.31.1


                 reply	other threads:[~2022-09-27 13:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=tencent_BAA30488EB06A842C1595097BA2A7FAF9908@qq.com \
    --to=rtoax@foxmail.com \
    --cc=amir73il@gmail.com \
    --cc=hca@linux.ibm.com \
    --cc=jack@suse.cz \
    --cc=krisman@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mike.leach@linaro.org \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®