From: Chao Yu <chao@kernel.org>
To: Prabhakar Pujeri <prabhakar.pujeri@dell.com>, fstests@vger.kernel.org
Cc: chao@kernel.org, Zorro Lang <zlang@kernel.org>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs/024: add missing execute permission
Date: Fri, 4 Sep 2026 07:35:58 +0800 [thread overview]
Message-ID: <4875d343-78ed-4a44-a479-f96b3847e8bd@kernel.org> (raw)
In-Reply-To: <20260831104142.2229-1-prabhakar.pujeri@dell.com>
On 8/31/26 18:41, Prabhakar Pujeri via Linux-f2fs-devel wrote:
> The test script was committed with mode 100644 while all other test
> scripts are 100755, so check fails to execute it directly with
> "Permission denied". Fix the file mode.
>
> Signed-off-by: Prabhakar Pujeri <prabhakar.pujeri@dell.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
prev parent reply other threads:[~2026-09-03 23:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 10:41 [PATCH] f2fs/024: add missing execute permission Prabhakar Pujeri
2026-09-02 14:39 ` Zorro Lang
2026-09-03 23:35 ` Chao Yu [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=4875d343-78ed-4a44-a479-f96b3847e8bd@kernel.org \
--to=chao@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=prabhakar.pujeri@dell.com \
--cc=zlang@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;
as well as URLs for NNTP newsgroup(s).