From: Kevin Hao <haokexin@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: "Kevin Hao" <haokexin@gmail.com>,
"Íñigo Huguet" <ihuguet@redhat.com>,
"Danny Lin" <danny@kdrag0n.dev>,
"Mickaël Salaün" <mic@digikod.net>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: [PATCH] .editorconfig: Respect .editorconfig settings from parent directories
Date: Wed, 17 Dec 2025 12:23:27 +0800 [thread overview]
Message-ID: <20251217-editconfig-v1-1-883e6dd6dbfa@gmail.com> (raw)
Setting 'root' to 'true' prevents the editor from searching for other
.editorconfig files in parent directories. However, a common workflow
involves generating a patch with 'git format-patch' and opening it in
an editor within the kernel source directory. In such cases, we want
any specific settings for patch files defined in an .editorconfig
located above the kernel source directory to remain effective.
Therefore, remove the 'root' setting from the kernel .editorconfig.
Signed-off-by: Kevin Hao <haokexin@gmail.com>
---
Cc: Íñigo Huguet <ihuguet@redhat.com>
Cc: Danny Lin <danny@kdrag0n.dev>
Cc: Mickaël Salaün <mic@digikod.net>
Cc: Masahiro Yamada <masahiroy@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
---
.editorconfig | 2 --
1 file changed, 2 deletions(-)
diff --git a/.editorconfig b/.editorconfig
index 29a30ccfc07bf2019cc05613c67ed35e02af6490..b5ea32b6954b9ae16b792a397b999da1eab6f95f 100644
--- a/.editorconfig
+++ b/.editorconfig
@@ -1,7 +1,5 @@
# SPDX-License-Identifier: GPL-2.0-only
-root = true
-
[{*.{awk,c,dts,dtsi,dtso,h,mk,s,S},Kconfig,Makefile,Makefile.*}]
charset = utf-8
end_of_line = lf
---
base-commit: 563c8dd425b59e44470e28519107b1efc99f4c7b
change-id: 20251217-editconfig-d600eb4d7152
Best regards,
--
Kevin Hao <haokexin@gmail.com>
reply other threads:[~2025-12-17 4:23 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=20251217-editconfig-v1-1-883e6dd6dbfa@gmail.com \
--to=haokexin@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=danny@kdrag0n.dev \
--cc=ihuguet@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mic@digikod.net \
/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®