From: Heiko Stuebner <heiko@sntech.de>
To: arm@kernel.org
Cc: soc@kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Rockchip soc fix for 5.16
Date: Mon, 13 Dec 2021 11:05:51 +0100 [thread overview]
Message-ID: <1827929.9bfCS3lLB7@phil> (raw)
The following changes since commit fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf:
Linux 5.16-rc1 (2021-11-14 13:56:52 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v5.16-rockchip-socfixes1
for you to fetch changes up to 423e85e97aaf69e5198bbec6811e3825c8b5019a:
ARM: rockchip: Use memcpy_toio instead of memcpy on smp bring-up (2021-11-21 18:24:31 +0100)
----------------------------------------------------------------
Prevent panic with FORTIFY_SOURCE in smp bringup.
----------------------------------------------------------------
Ivan T. Ivanov (1):
ARM: rockchip: Use memcpy_toio instead of memcpy on smp bring-up
arch/arm/mach-rockchip/platsmp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: arm@kernel.org
Cc: soc@kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Rockchip soc fix for 5.16
Date: Mon, 13 Dec 2021 11:05:51 +0100 [thread overview]
Message-ID: <1827929.9bfCS3lLB7@phil> (raw)
The following changes since commit fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf:
Linux 5.16-rc1 (2021-11-14 13:56:52 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v5.16-rockchip-socfixes1
for you to fetch changes up to 423e85e97aaf69e5198bbec6811e3825c8b5019a:
ARM: rockchip: Use memcpy_toio instead of memcpy on smp bring-up (2021-11-21 18:24:31 +0100)
----------------------------------------------------------------
Prevent panic with FORTIFY_SOURCE in smp bringup.
----------------------------------------------------------------
Ivan T. Ivanov (1):
ARM: rockchip: Use memcpy_toio instead of memcpy on smp bring-up
arch/arm/mach-rockchip/platsmp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: arm@kernel.org
Cc: soc@kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Rockchip soc fix for 5.16
Date: Mon, 13 Dec 2021 11:05:51 +0100 [thread overview]
Message-ID: <1827929.9bfCS3lLB7@phil> (raw)
The following changes since commit fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf:
Linux 5.16-rc1 (2021-11-14 13:56:52 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v5.16-rockchip-socfixes1
for you to fetch changes up to 423e85e97aaf69e5198bbec6811e3825c8b5019a:
ARM: rockchip: Use memcpy_toio instead of memcpy on smp bring-up (2021-11-21 18:24:31 +0100)
----------------------------------------------------------------
Prevent panic with FORTIFY_SOURCE in smp bringup.
----------------------------------------------------------------
Ivan T. Ivanov (1):
ARM: rockchip: Use memcpy_toio instead of memcpy on smp bring-up
arch/arm/mach-rockchip/platsmp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-12-13 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 10:05 Heiko Stuebner [this message]
2021-12-13 10:05 ` [GIT PULL] Rockchip soc fix for 5.16 Heiko Stuebner
2021-12-13 10:05 ` Heiko Stuebner
2021-12-13 14:20 ` patchwork-bot+linux-soc
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=1827929.9bfCS3lLB7@phil \
--to=heiko@sntech.de \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@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.