From: Dinh Nguyen <dinguyen@kernel.org>
To: arm@kernel.org, soc@kernel.org
Cc: dinguyen@kernel.org
Subject: [GIT PULL] ARM: socfpga: fix for v5.16
Date: Fri, 19 Nov 2021 09:32:24 -0600 [thread overview]
Message-ID: <20211119153224.2761257-1-dinguyen@kernel.org> (raw)
Hi Arnd/Olof,
please pull in this fix for v5.16.
Thanks,
Dinh
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/dinguyen/linux.git tags/socfpga_fix_for_v5.16
for you to fetch changes up to 187bea472600dcc8d2eb714335053264dd437172:
ARM: socfpga: Fix crash with CONFIG_FORTIRY_SOURCE (2021-11-18 16:19:40 -0600)
----------------------------------------------------------------
SoCFPGA fix for v5.16
- Fix crash when CONFIG_FORTIRY_SOURCE is enabled
----------------------------------------------------------------
Takashi Iwai (1):
ARM: socfpga: Fix crash with CONFIG_FORTIRY_SOURCE
arch/arm/mach-socfpga/core.h | 2 +-
arch/arm/mach-socfpga/platsmp.c | 8 ++++----
2 files changed, 5 insertions(+), 5 deletions(-)
next reply other threads:[~2021-11-19 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 15:32 Dinh Nguyen [this message]
2021-11-22 11:08 ` [GIT PULL] ARM: socfpga: fix for v5.16 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=20211119153224.2761257-1-dinguyen@kernel.org \
--to=dinguyen@kernel.org \
--cc=arm@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox