From: Zorro Lang <zlang@kernel.org>
To: Li Zhijian <lizhijian@fujitsu.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] xfs: Fix no executable permission
Date: Mon, 4 Mar 2024 12:31:00 +0800 [thread overview]
Message-ID: <20240304043100.r4q56itxuzx6dzn2@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com> (raw)
In-Reply-To: <20240115005913.3829532-1-lizhijian@fujitsu.com>
On Mon, Jan 15, 2024 at 08:59:13AM +0800, Li Zhijian wrote:
> Give them the executable permission, this also make the git status keep clean
> after `./check`
>
> Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
> ---
I tried to wait a few weeks to check if we have some patches to touch
these cases, then I can change the permission with that change together.
But looks like I have no chance :) So let's have this patch.
Reviewed-by: Zorro Lang <zlang@redhat.com>
We've changed to mvtest tool, to make sure the permission bit of new case,
I'll also add a testing step to check the permission bits later,
thanks for this fix.
Thanks,
Zorro
> tests/xfs/557 | 0
> tests/xfs/567 | 0
> tests/xfs/568 | 0
> 3 files changed, 0 insertions(+), 0 deletions(-)
> mode change 100644 => 100755 tests/xfs/557
> mode change 100644 => 100755 tests/xfs/567
> mode change 100644 => 100755 tests/xfs/568
>
> diff --git a/tests/xfs/557 b/tests/xfs/557
> old mode 100644
> new mode 100755
> diff --git a/tests/xfs/567 b/tests/xfs/567
> old mode 100644
> new mode 100755
> diff --git a/tests/xfs/568 b/tests/xfs/568
> old mode 100644
> new mode 100755
> --
> 2.29.2
>
>
prev parent reply other threads:[~2024-03-04 4:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 0:59 [PATCH] xfs: Fix no executable permission Li Zhijian
2024-03-04 4:31 ` Zorro Lang [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=20240304043100.r4q56itxuzx6dzn2@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com \
--to=zlang@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=lizhijian@fujitsu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).