From: Mike Rapoport <rppt@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ard Biesheuvel <ardb@kernel.org>,
Max Filippov <jcmvbkbc@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-xtensa@linux-xtensa.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Fix highmem initialization on arm and xtensa
Date: Thu, 5 Nov 2020 14:58:27 +0200 [thread overview]
Message-ID: <20201105125827.GA301837@kernel.org> (raw)
Hi Linus,
The following changes since commit 4ef8451b332662d004df269d4cdeb7d9f31419b5:
Merge tag 'perf-tools-for-v5.10-2020-11-03' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux (2020-11-03 13:28:50 -0800)
are available in the Git repository at:
ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/rppt/memblock.git tags/fixes-2020-11-05
for you to fetch changes up to b9bc36704cca500e2b41be4c5bf615c1d7ddc3ce:
ARM, xtensa: highmem: avoid clobbering non-page aligned memory reservations (2020-11-04 10:42:57 +0200)
----------------------------------------------------------------
Fix highmem initialization on arm and xtensa
Recent refactoring of memblock iterators has broken initialization of
highmem on arm and xtensa because it changed the way beginning and end of
memory regions are rounded to PFNs. This fix restores the original
behaviour.
----------------------------------------------------------------
Ard Biesheuvel (1):
ARM, xtensa: highmem: avoid clobbering non-page aligned memory reservations
arch/arm/mm/init.c | 4 ++--
arch/xtensa/mm/init.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
--
Sincerely yours,
Mike.
next reply other threads:[~2020-11-05 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 12:58 Mike Rapoport [this message]
2020-11-05 20:21 ` [GIT PULL] Fix highmem initialization on arm and xtensa pr-tracker-bot
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=20201105125827.GA301837@kernel.org \
--to=rppt@kernel.org \
--cc=ardb@kernel.org \
--cc=jcmvbkbc@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=torvalds@linux-foundation.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).