From: "Nghia Le" <nghialm78@gmail.com>
Cc: Nghia Le <nghialm78@gmail.com>, linux-safety@lists.elisa.tech
Subject: [linux-safety] [PATCH v2] parse-sublevel-options.h : Add missing newline
Date: Thu, 19 Aug 2021 17:04:51 +0700 [thread overview]
Message-ID: <20210819100451.87747-1-nghialm78@gmail.com> (raw)
Add missing newline at the end of file, thus removing relevant warning
reported by checkpatch.pl
Checkpatch.pl reported for patch as below:
total: 0 errors, 0 warnings, 6 lines checked
v2-0001-parse-sublevel-options.h-Add-missing-newline.patch has no obvious
style problems and is ready for submission.
Signed-off-by: Nghia Le <nghialm78@gmail.com>
---
tools/perf/util/parse-sublevel-options.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/util/parse-sublevel-options.h b/tools/perf/util/parse-sublevel-options.h
index 9b9efcc2aaad..578b18ef03bb 100644
--- a/tools/perf/util/parse-sublevel-options.h
+++ b/tools/perf/util/parse-sublevel-options.h
@@ -8,4 +8,4 @@ struct sublevel_option {
int perf_parse_sublevel_options(const char *str, struct sublevel_option *opts);
-#endif
\ No newline at end of file
+#endif
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#243): https://lists.elisa.tech/g/linux-safety/message/243
Mute This Topic: https://lists.elisa.tech/mt/84993288/5278000
Group Owner: linux-safety+owner@lists.elisa.tech
Unsubscribe: https://lists.elisa.tech/g/linux-safety/unsub [linux-safety@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next reply other threads:[~2021-08-19 10:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 10:04 Nghia Le [this message]
2021-08-19 10:16 ` [linux-safety] [PATCH v2] parse-sublevel-options.h : Add missing newline Lukas Bulwahn
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=20210819100451.87747-1-nghialm78@gmail.com \
--to=nghialm78@gmail.com \
--cc=linux-safety@lists.elisa.tech \
/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;
as well as URLs for NNTP newsgroup(s).