From: Dinh Nguyen <dinguyen@kernel.org>
To: Sasha Levin <sashal@kernel.org>, linux-arm-kernel@lists.infradead.org
Cc: devicetree@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 2/3] arm64: dts: stratix10: add status to qspi dts node
Date: Fri, 10 Jul 2020 10:27:23 -0500 [thread overview]
Message-ID: <7fb07b88-611f-532b-ed7e-108baadf43c5@kernel.org> (raw)
In-Reply-To: <20200710140244.6097C207BB@mail.kernel.org>
Please apply to v5.7.7
Thanks,
Dinh
On 7/10/20 9:02 AM, Sasha Levin wrote:
> Hi
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag
> fixing commit: 0cb140d07fc7 ("arm64: dts: stratix10: Add QSPI support for Stratix10").
>
> The bot has tested the following trees: v5.7.7, v5.4.50, v4.19.131.
>
> v5.7.7: Build OK!
> v5.4.50: Failed to apply! Possible dependencies:
> 3c0f3b8545e79 ("arm64: dts: add NAND board files for Stratix10 and Agilex")
>
> v4.19.131: Failed to apply! Possible dependencies:
> 116edf6e5239e ("MIPS: mscc: add DT for Ocelot PCB120")
> 1ac832509f2ea ("nds32: Support FP emulation")
> 387181dcdb6c1 ("RISC-V: Always compile mm/init.c with cmodel=medany and notrace")
> 3c0f3b8545e79 ("arm64: dts: add NAND board files for Stratix10 and Agilex")
> 4b36daf9ada30 ("arm64: dts: agilex: Add initial support for Intel's Agilex SoCFPGA")
> 704cfd7f5f71c ("ARM: sti: remove pen_release and boot_lock")
> 78e3dbc166a13 ("ARM: Prepare RDA8810PL SoC")
> 7938e6315c9af ("nds32: Power management for nds32")
> 9671f7061433e ("Allow to disable FPU support")
> 9fb29c734f9e9 ("ARM: milbeaut: Add basic support for Milbeaut m10v SoC")
> c32e64e852f3f ("csky: Build infrastructure")
> c4c14c3bd177e ("csky: remove builtin-dtb Kbuild")
> e46bf83c1864a ("nds32: nds32 FPU port")
> ebd09753b5707 ("nds32: Perf porting")
> ec8f24b7faaf3 ("treewide: Add SPDX license identifier - Makefile/Kconfig")
>
>
> NOTE: The patch will not be queued to stable trees until it is upstream.
>
> How should we proceed with this patch?
>
_______________________________________________
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:[~2020-07-10 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 20:39 [PATCH 1/3] arm64: dts: agilex: add status to qspi dts node Dinh Nguyen
2020-06-29 20:39 ` [PATCH 2/3] arm64: dts: stratix10: " Dinh Nguyen
2020-07-10 14:02 ` Sasha Levin
2020-07-10 15:27 ` Dinh Nguyen [this message]
2020-07-10 15:27 ` Dinh Nguyen
2020-06-29 20:39 ` [PATCH 3/3] arm64: dts: stratix10: increase QSPI reg address in nand dts file Dinh Nguyen
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=7fb07b88-611f-532b-ed7e-108baadf43c5@kernel.org \
--to=dinguyen@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--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).