From: Michal Simek <monstr@monstr.eu>
To: arm-soc <arm@kernel.org>, soc@kernel.org, git <git@xilinx.com>
Cc: linux-arm <linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL] ARM: soc: Xilinx SoC changes for v5.6
Date: Tue, 21 Jan 2020 11:09:40 +0100 [thread overview]
Message-ID: <50dec3cf-5f80-69be-c3d1-cc14b9bce5ff@monstr.eu> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1225 bytes --]
Hi,
please pull this one patch to your tree. It is fixing kexec/crash kernel
cpu startup handling.
Thanks,
Michal
The following changes since commit e42617b825f8073569da76dc4510bfa019b1c35a:
Linux 5.5-rc1 (2019-12-08 14:57:55 -0800)
are available in the Git repository at:
https://github.com/Xilinx/linux-xlnx.git tags/zynq-soc-for-v5.6
for you to fetch changes up to 6c6b3f1f260b24dc0ab9cbbf369e4fa36819ab8b:
ARM: zynq: use physical cpuid in zynq_slcr_cpu_stop/start (2020-01-08
15:21:09 +0100)
----------------------------------------------------------------
ARM: Xilinx Zynq SoC patches for v5.6
- Fix cpuid handling logic in platform SMP startup code
----------------------------------------------------------------
Quanyang Wang (1):
ARM: zynq: use physical cpuid in zynq_slcr_cpu_stop/start
arch/arm/mach-zynq/platsmp.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal SoCs
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2020-01-21 10:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=50dec3cf-5f80-69be-c3d1-cc14b9bce5ff@monstr.eu \
--to=monstr@monstr.eu \
--cc=arm@kernel.org \
--cc=git@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=soc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.