From: Tom Rix <trix@redhat.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/8xx: select CPM1 for MPC8XXFADS
Date: Wed, 2 Jun 2021 15:10:37 -0700 [thread overview]
Message-ID: <d50f61b0-e165-b3d3-d278-ef0514ddccc0@redhat.com> (raw)
In-Reply-To: <50ed000a-c1af-8552-9d35-771b3bc131e5@csgroup.eu>
On 6/2/21 12:44 AM, Christophe Leroy wrote:
>
>
> Le 01/06/2021 à 19:53, trix@redhat.com a écrit :
>> From: Tom Rix <trix@redhat.com>
>>
>> With MPC8XXFADS, there is this linker error
>> ppc64-linux-ld: m8xx_setup.o: in function `cpm_cascade':
>> m8xx_setup.c: undefined reference to `cpm_get_irq'
>
> It looks like this config item is stale, it doesn't build any board
> support, there is no define_machine() for this config item, no file is
> linked to that config item.
>
> I think you should just remove that item from the possible choices.
>
Yes, this looks like a dead config and removing it is what to do.
I withdraw this change.
I am looking at sweeping the tree of dead configs.
Up a dir, my finder shows
PPC_MMU_NOHASH_32
is another (maybe) dead config.
Thanks for pointing this out,
Tom
> Christophe
>
>
>>
>> cpm_get_irq() is conditionally complied by CPM1
>> So add a select, like the other plaforms
>>
>> Signed-off-by: Tom Rix <trix@redhat.com>
>> ---
>> arch/powerpc/platforms/8xx/Kconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/arch/powerpc/platforms/8xx/Kconfig
>> b/arch/powerpc/platforms/8xx/Kconfig
>> index 60cc5b537a98..919082cdb2f1 100644
>> --- a/arch/powerpc/platforms/8xx/Kconfig
>> +++ b/arch/powerpc/platforms/8xx/Kconfig
>> @@ -10,6 +10,7 @@ choice
>> config MPC8XXFADS
>> bool "FADS"
>> + select CPM1
>> config MPC86XADS
>> bool "MPC86XADS"
>>
>
prev parent reply other threads:[~2021-06-02 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 17:53 [PATCH] powerpc/8xx: select CPM1 for MPC8XXFADS trix
2021-06-02 7:44 ` Christophe Leroy
2021-06-02 22:10 ` Tom Rix [this message]
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=d50f61b0-e165-b3d3-d278-ef0514ddccc0@redhat.com \
--to=trix@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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).