From: bugzilla-daemon@kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 215567] build failure when PPC_64S_HASH_MMU=n is selected in kernel .config
Date: Tue, 01 Mar 2022 22:30:09 +0000 [thread overview]
Message-ID: <bug-215567-206035-liY5rUQ2KS@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215567-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215567
--- Comment #5 from Erhard F. (erhard_f@mailbox.org) ---
Your 2nd patch solved the issue. Thanks Murilo!
Build completes and the Talos boots fine into the patched 5.17-rc5.
--
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-01 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 13:00 [Bug 215567] New: build failure when PPC_64S_HASH_MMU=n is selected in kernel .config bugzilla-daemon
2022-03-01 17:20 ` [Bug 215567] " bugzilla-daemon
2022-03-01 18:42 ` bugzilla-daemon
2022-03-01 19:57 ` bugzilla-daemon
2022-03-01 20:52 ` bugzilla-daemon
2022-03-01 22:30 ` bugzilla-daemon [this message]
2022-03-12 13:22 ` 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-215567-206035-liY5rUQ2KS@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).