From: Brandon Pollack <brpol@chromium.org>
To: linux-kernel@vger.kernel.org
Cc: dan.carpenter@linaro.org, masahiroy@kernel.org, ojeda@kernel.org,
alex.gaynor@gmail.com, keescook@chromium.org, nathan@kernel.org,
Brandon Pollack <brpol@chromium.org>
Subject: [PATCH v2] .gitignore: ignore smatch generated files
Date: Mon, 8 May 2023 05:52:28 +0000 [thread overview]
Message-ID: <20230508055226.3183447-1-brpol@chromium.org> (raw)
ignore smatch generated files.
Change-Id: I8ca4002128e53024ea8a3daef908ec5e49cec65c
Signed-off-by: Brandon Pollack <brpol@chromium.org>
---
v2: Removed trinity stuff
New to development and looking for tasks to work on to get familiar with
code, I noticed smatch generates some files at the root. Since this
tool seems frequent for newbies like myself I thought it would be worth
getting rid of the chance of accidentally committing these files.
---
.gitignore | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/.gitignore b/.gitignore
index 47229f98b327..fd8572cb7db7 100644
--- a/.gitignore
+++ b/.gitignore
@@ -171,3 +171,10 @@ sphinx_*/
# Rust analyzer configuration
/rust-project.json
+
+# Smatch tree outputs
+smatch_compile.warns
+smatch_db.sqlite
+smatch_warns.txt
+smatch_warns.txt.caller_info
+smatch_warns.txt.sql
--
2.40.1.521.gf1e218fcd8-goog
next reply other threads:[~2023-05-08 5:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 5:52 Brandon Pollack [this message]
2023-05-08 5:58 ` Dan Carpenter
2023-05-08 9:29 ` Miguel Ojeda
2023-05-08 9:42 ` Dan Carpenter
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=20230508055226.3183447-1-brpol@chromium.org \
--to=brpol@chromium.org \
--cc=alex.gaynor@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ojeda@kernel.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®