From: Alex Deucher <alexdeucher@gmail.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
"Huang Rui" <ray.huang@amd.com>,
"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>,
"Christian König" <christian.koenig@amd.com>,
"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/amdgpu: remove unintended executable mode
Date: Mon, 5 Oct 2020 15:18:49 -0400 [thread overview]
Message-ID: <CADnq5_M4nagoEoVYL011ysVDZyWp3hKQjfO97GQuvyeW-_QdWQ@mail.gmail.com> (raw)
In-Reply-To: <20201004064917.17941-1-lukas.bulwahn@gmail.com>
On Mon, Oct 5, 2020 at 3:22 AM Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:
>
> Besides the intended change, commit 3437f5f6c979 ("drm/amdgpu: add gfx
> support for van gogh (v2)") also set the source files gfx_v10_0.c to be
> executable, i.e., changed from old mode 644 to new mode 755.
>
> Set to the usual mode for source and headers files. No functional change.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Luben already sent out a similar patch. Fixed up and will be pushed out soon.
Alex
> ---
> applies cleanly on next-20201002
>
> Alex, please pick this minor non-urgent cleanup patch on your -next tree.
>
> Huang Rui, please ack. You might want to check your development environment
> introducing those executable modes on files.
>
> drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c | 0
> 1 file changed, 0 insertions(+), 0 deletions(-)
> mode change 100755 => 100644 drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c b/drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c
> old mode 100755
> new mode 100644
> --
> 2.17.1
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2020-10-05 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 6:49 [PATCH] drm/amdgpu: remove unintended executable mode Lukas Bulwahn
2020-10-05 19:18 ` Alex Deucher [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=CADnq5_M4nagoEoVYL011ysVDZyWp3hKQjfO97GQuvyeW-_QdWQ@mail.gmail.com \
--to=alexdeucher@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=ray.huang@amd.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 NNTP newsgroup(s).