From: Johan Hovold <johan@kernel.org>
To: kernel test robot <lkp@intel.com>, Sasha Levin <sashal@kernel.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Johan Hovold <johan+linaro@kernel.org>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [linux-stable-rc:linux-5.19.y 2987/3450] arch/arm64/boot/dts/qcom/sc8280xp-crd.dts:12:10: fatal error: 'sc8280xp.dtsi' file not found
Date: Tue, 18 Oct 2022 09:16:17 +0200 [thread overview]
Message-ID: <Y05Swd1ZRAF4SnTV@hovoldconsulting.com> (raw)
In-Reply-To: <202210181441.Uo9b9Ie7-lkp@intel.com>
On Tue, Oct 18, 2022 at 02:50:44PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.19.y
> head: 28b57a08d7fd284fdeb0c92ce4aeea9bcd023911
> commit: c4c72ceb23b538b6cbcc9cbf9463b71c3e2ae933 [2987/3450] arm64: dts: qcom: sc8280xp: Add reference device
> config: arm64-randconfig-r011-20221017
> compiler: clang version 16.0.0 (https://github.com/llvm/llvm-project 791a7ae1ba3efd6bca96338e10ffde557ba83920)
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # install arm64 cross compiling tool for clang build
> # apt-get install binutils-aarch64-linux-gnu
> # https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?id=c4c72ceb23b538b6cbcc9cbf9463b71c3e2ae933
Sasha, why on earth are you backporting commit ccd3517faf18 ("arm64:
dts: qcom: sc8280xp: Add reference device")?!
It seems your implementation of the stable-tree process has gone
completely off rails.
Johan
next prev parent reply other threads:[~2022-10-18 7:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 6:50 [linux-stable-rc:linux-5.19.y 2987/3450] arch/arm64/boot/dts/qcom/sc8280xp-crd.dts:12:10: fatal error: 'sc8280xp.dtsi' file not found kernel test robot
2022-10-18 7:16 ` Johan Hovold [this message]
2022-10-18 7:51 ` Greg Kroah-Hartman
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=Y05Swd1ZRAF4SnTV@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=johan+linaro@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=sashal@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