From: Joel Stanley <joel@jms.id.au>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
Michael Neuling <mikey@neuling.org>,
Benjamin Herrenschmidt <benh@ozlabs.org>
Subject: Re: [PATCH RFC 1/4] powerpc/radix: Fix compilation for radix with CONFIG_SMP=n
Date: Thu, 14 May 2020 08:26:15 +0000 [thread overview]
Message-ID: <CACPK8XdGSc++=6MMh_zmhczwep53M_Y7H-WqtatCvB4F8DWyVQ@mail.gmail.com> (raw)
In-Reply-To: <1589010661.v7yharjogg.astroid@bobo.none>
On Sat, 9 May 2020 at 07:52, Nicholas Piggin <npiggin@gmail.com> wrote:
>
> Excerpts from Paul Mackerras's message of May 9, 2020 3:02 pm:
> > This fixes the compile errors we currently get with CONFIG_SMP=n and
> > CONFIG_PPC_RADIX_MMU=y.
>
> Did I already fix this, or does it keep getting broken?! :(
>
> Anyway fine by me if it's required.
You're right, your fix was merged in 5.7-rc1.
Cheers,
Joel
next prev parent reply other threads:[~2020-05-14 8:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 5:01 [PATCH RFC 0/4] Add support for Microwatt-based SoCs Paul Mackerras
2020-05-09 5:02 ` [PATCH RFC 1/4] powerpc/radix: Fix compilation for radix with CONFIG_SMP=n Paul Mackerras
2020-05-09 7:52 ` Nicholas Piggin
2020-05-14 8:26 ` Joel Stanley [this message]
2020-05-09 5:02 ` [PATCH RFC 2/4] powerpc: Add Microwatt platform Paul Mackerras
2020-05-09 7:58 ` Nicholas Piggin
2020-05-09 8:36 ` Alistair Popple
2020-05-09 9:10 ` Nicholas Piggin
2020-05-12 1:56 ` Michael Ellerman
2020-05-09 5:03 ` [PATCH RFC 3/4] powerpc/microwatt: Add early debug UART support for Microwatt Paul Mackerras
2020-05-11 7:07 ` Segher Boessenkool
2020-05-12 1:57 ` Michael Ellerman
2020-05-09 5:04 ` [PATCH RFC 4/4] powerpc/radix: Add support for microwatt's PRTBL SPR Paul Mackerras
2020-05-09 8:02 ` Nicholas Piggin
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='CACPK8XdGSc++=6MMh_zmhczwep53M_Y7H-WqtatCvB4F8DWyVQ@mail.gmail.com' \
--to=joel@jms.id.au \
--cc=benh@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.org \
--cc=npiggin@gmail.com \
/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).