All of lore.kernel.org
 help / color / mirror / Atom feed
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 17:20:59 +0000	[thread overview]
Message-ID: <bug-215567-206035-QZqT1ygghB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215567-206035@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=215567

Murilo Opsfelder Araújo (mopsfelder@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mopsfelder@gmail.com

--- Comment #1 from Murilo Opsfelder Araújo (mopsfelder@gmail.com) ---
Hi, Erhard.

Thanks for reporting the issue.
I've sent a fix proposal for this:

https://lists.ozlabs.org/pipermail/linuxppc-dev/2022-March/240698.html

Please let me know if the proposed fix worked for you.
You can reply here on Bugzilla or to the list with your 'Tested-by:' tag.

Thank you!
Murilo

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  reply	other threads:[~2022-03-01 17:21 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 ` bugzilla-daemon [this message]
2022-03-01 18:42 ` [Bug 215567] " bugzilla-daemon
2022-03-01 19:57 ` bugzilla-daemon
2022-03-01 20:52 ` bugzilla-daemon
2022-03-01 22:30 ` bugzilla-daemon
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-QZqT1ygghB@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.