From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64 fixes for 4.10-rc6
Date: Sat, 28 Jan 2017 10:27:05 +0000 [thread overview]
Message-ID: <20170128102702.GA15956@e104818-lin.cambridge.arm.com> (raw)
Hi Linus,
Please pull the arm64 fix for 4.10 below. Thanks.
The following changes since commit 7a308bb3016f57e5be11a677d15b821536419d36:
Linux 4.10-rc5 (2017-01-22 12:54:15 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes
for you to fetch changes up to 606f42265d384b9149bfb953c5dfc6d4710fef4c:
arm64: skip register_cpufreq_notifier on ACPI-based systems (2017-01-27 11:30:36 +0000)
----------------------------------------------------------------
- Fix kernel panic on ACPI-based systems where CPU capacity description
is not currently handled
----------------------------------------------------------------
Prashanth Prakash (1):
arm64: skip register_cpufreq_notifier on ACPI-based systems
arch/arm64/kernel/topology.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
--
Catalin
reply other threads:[~2017-01-28 10:27 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=20170128102702.GA15956@e104818-lin.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).