devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Peter Geis <pgwipeout@gmail.com>,
	Heiko Stuebner <heiko@sntech.de>, Sasha Levin <sashal@kernel.org>,
	linux-stable <stable@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	lkft-triage@lists.linaro.org
Subject: Re: [stable-rc queue/5/15 ]: rk3568-evb1-v10.dts:10:10: fatal error: rk3568.dtsi: No such file or directory
Date: Mon, 15 Nov 2021 13:27:14 +0100	[thread overview]
Message-ID: <YZJSIvb3JF6dIsgx@kroah.com> (raw)
In-Reply-To: <CA+G9fYsZ_Zks32WTNgKjQg2gwRuqS4E92ttH+okUCdnPFdaNTQ@mail.gmail.com>

On Mon, Nov 15, 2021 at 12:25:50PM +0530, Naresh Kamboju wrote:
> Following build warnings/ errors noticed on Linux stable-rc queue/5.15 branch.
> with gcc-11 for arm64 architecture.
> 
> arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi:464.3-52: Warning
> (pci_device_reg): /pcie@f8000000/pcie@0,0:reg: PCI reg address is not
> configuration space
> arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi:464.3-52: Warning
> (pci_device_reg): /pcie@f8000000/pcie@0,0:reg: PCI reg address is not
> configuration space
> arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi:464.3-52: Warning
> (pci_device_reg): /pcie@f8000000/pcie@0,0:reg: PCI reg address is not
> configuration space
> arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi:464.3-52: Warning
> (pci_device_reg): /pcie@f8000000/pcie@0,0:reg: PCI reg address is not
> configuration space
> arch/arm64/boot/dts/rockchip/rk3568-evb1-v10.dts:10:10: fatal error:
> rk3568.dtsi: No such file or directory
>    10 | #include rk3568.dtsi
>       |          ^~~~~~~~~~~~~
> compilation terminated.
> make[3]: *** [scripts/Makefile.lib:358:
> arch/arm64/boot/dts/rockchip/rk3568-evb1-v10.dtb] Error 1
> 
> The first bad commit:
> --------
> arm64: dts: rockchip: move rk3568 dtsi to rk356x dtsi
> [ Upstream commit 4e50d2173b67115a5574f4f4ce64ec9c5d9c136e ]
> 
> In preparation for separating the rk3568 and rk3566 device trees, move
> the base rk3568 dtsi to rk356x dtsi.
> This will allow us to strip out the rk3568 specific nodes.
> 
> Signed-off-by: Peter Geis <pgwipeout@gmail.com>
> Link: https://lore.kernel.org/r/20210710151034.32857-2-pgwipeout@gmail.com
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> Signed-off-by: Sasha Levin <sashal@kernel.org
> 
> 
> 
> Build config:
> https://builds.tuxbuild.com/20wHY13986hVAE9j4Kwxq4C8JUX/config
> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>

Now dropped, thanks.

greg k-h

      reply	other threads:[~2021-11-15 12:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15  6:55 [stable-rc queue/5/15 ]: rk3568-evb1-v10.dts:10:10: fatal error: rk3568.dtsi: No such file or directory Naresh Kamboju
2021-11-15 12:27 ` Greg Kroah-Hartman [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=YZJSIvb3JF6dIsgx@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=pgwipeout@gmail.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.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).