From: Peng Fan <peng.fan@nxp.com>
To: Marcel Ziswiler <marcel@ziswiler.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Aisheng Dong <aisheng.dong@nxp.com>,
Fabio Estevam <festevam@gmail.com>, Jacky Bai <ping.bai@nxp.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
dl-linux-imx <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v1 3/5] arm64: dts: imx8ulp: no executable source file permission
Date: Mon, 29 Aug 2022 05:41:18 +0000 [thread overview]
Message-ID: <DU0PR04MB9417C07E03D931C982B1645888769@DU0PR04MB9417.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20220826192252.794651-4-marcel@ziswiler.com>
> Subject: [PATCH v1 3/5] arm64: dts: imx8ulp: no executable source file
> permission
>
> From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
>
> This fixes the following error:
>
> arch/arm64/boot/dts/freescale/imx8ulp-pinfunc.h: error: do not set
> execute permissions for source files
>
> Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
Acked-by: Peng Fan <peng.fan@nxp.com>
> ---
>
> arch/arm64/boot/dts/freescale/imx8ulp-pinfunc.h | 0
> 1 file changed, 0 insertions(+), 0 deletions(-) mode change 100755 =>
> 100644 arch/arm64/boot/dts/freescale/imx8ulp-pinfunc.h
>
> diff --git a/arch/arm64/boot/dts/freescale/imx8ulp-pinfunc.h
> b/arch/arm64/boot/dts/freescale/imx8ulp-pinfunc.h
> old mode 100755
> new mode 100644
> --
> 2.36.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-08-29 5:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 19:22 [PATCH v1 0/5] ARM: arm64: dts/clk: imx: indentation permission whitespace cleanup 2 Marcel Ziswiler
2022-08-26 19:22 ` [PATCH v1 1/5] ARM: dts: imx6sl: use tabs for code indent Marcel Ziswiler
2022-09-05 1:57 ` Shawn Guo
2022-08-26 19:22 ` [PATCH v1 2/5] ARM: dts: imx6sx-udoo-neo: don't use multiple blank lines Marcel Ziswiler
2022-09-05 2:01 ` Shawn Guo
2022-08-26 19:22 ` [PATCH v1 3/5] arm64: dts: imx8ulp: no executable source file permission Marcel Ziswiler
2022-08-29 5:41 ` Peng Fan [this message]
2022-09-05 1:53 ` Shawn Guo
2022-08-26 19:22 ` [PATCH v1 4/5] clk: imx6sll: add proper spdx license identifier Marcel Ziswiler
2022-08-29 9:40 ` Abel Vesa
2022-08-30 21:13 ` Rob Herring
2022-09-23 13:28 ` Marcel Ziswiler
2022-08-26 19:22 ` [PATCH v1 5/5] dt-bindings: imx8ulp: clock: no spaces before tabs Marcel Ziswiler
2022-08-27 17:23 ` Krzysztof Kozlowski
2022-08-29 9:40 ` Abel Vesa
2022-09-23 13:29 ` Marcel Ziswiler
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=DU0PR04MB9417C07E03D931C982B1645888769@DU0PR04MB9417.eurprd04.prod.outlook.com \
--to=peng.fan@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=marcel@ziswiler.com \
--cc=ping.bai@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).