From: Borislav Petkov <bp@alien8.de>
To: Kuan-Wei Chiu <visitorckw@gmail.com>
Cc: tony.luck@intel.com, james.morse@arm.com, mchehab@kernel.org,
rric@kernel.org, shiju.jose@huawei.com,
jonathan.cameron@huawei.com, jserv@ccns.ncku.edu.tw,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] EDAC: Fix wrong executable file modes for C source files
Date: Sat, 30 Aug 2025 17:49:02 +0200 [thread overview]
Message-ID: <20250830154902.GCaLMdbp6eeHS9_IO0@fat_crate.local> (raw)
In-Reply-To: <20250828191954.903125-1-visitorckw@gmail.com>
On Fri, Aug 29, 2025 at 03:19:54AM +0800, Kuan-Wei Chiu wrote:
> Three EDAC source files were mistakenly marked as executable in
> commit 1e14ea901dc8 ("EDAC: Initialize EDAC features sysfs attributes").
>
> These are plain C source files and should not carry the executable bit.
> Correcting their modes follows the principle of least privilege and
> avoids unnecessary execute permissions in the repository.
>
> Fixes: 1e14ea901dc8 ("EDAC: Initialize EDAC features sysfs attributes")
> Signed-off-by: Kuan-Wei Chiu <visitorckw@gmail.com>
> ---
> drivers/edac/ecs.c | 0
> drivers/edac/mem_repair.c | 0
> drivers/edac/scrub.c | 0
> 3 files changed, 0 insertions(+), 0 deletions(-)
> mode change 100755 => 100644 drivers/edac/ecs.c
> mode change 100755 => 100644 drivers/edac/mem_repair.c
> mode change 100755 => 100644 drivers/edac/scrub.c
>
> diff --git a/drivers/edac/ecs.c b/drivers/edac/ecs.c
> old mode 100755
> new mode 100644
> diff --git a/drivers/edac/mem_repair.c b/drivers/edac/mem_repair.c
> old mode 100755
> new mode 100644
> diff --git a/drivers/edac/scrub.c b/drivers/edac/scrub.c
> old mode 100755
> new mode 100644
> --
Applied, thanks.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2025-08-30 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 19:19 Kuan-Wei Chiu
2025-08-30 15:49 ` Borislav Petkov [this message]
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=20250830154902.GCaLMdbp6eeHS9_IO0@fat_crate.local \
--to=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=jonathan.cameron@huawei.com \
--cc=jserv@ccns.ncku.edu.tw \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rric@kernel.org \
--cc=shiju.jose@huawei.com \
--cc=tony.luck@intel.com \
--cc=visitorckw@gmail.com \
/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®