From: bugzilla-daemon@kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 215781] Highmem support broken on kernels greater 5.15.x on ppc32?
Date: Thu, 31 Mar 2022 06:21:35 +0000 [thread overview]
Message-ID: <bug-215781-206035-HXyJlD9XCE@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215781-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215781
--- Comment #4 from Christophe Leroy (christophe.leroy@csgroup.eu) ---
This problem was introduced in 5.15 by commit 602946ec2f90 ("powerpc: Set
max_mapnr correctly")
A similar issue has been opened at
https://github.com/linuxppc/issues/issues/399
Following series should fix it:
https://patchwork.ozlabs.org/project/linuxppc-dev/list/?state=*&series=286464
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-03-31 6:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 22:52 [Bug 215781] New: Highmem support broken on kernels greater 5.15.x on ppc32? bugzilla-daemon
2022-03-30 22:54 ` [Bug 215781] " bugzilla-daemon
2022-03-30 22:55 ` bugzilla-daemon
2022-03-30 22:55 ` bugzilla-daemon
2022-03-31 6:21 ` bugzilla-daemon [this message]
2022-04-18 10:49 ` bugzilla-daemon
2022-04-18 10:49 ` bugzilla-daemon
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=bug-215781-206035-HXyJlD9XCE@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).