From: "Pali Rohár" <pali@kernel.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Li Yang <leoyang.li@nxp.com>, Scott Wood <oss@buserror.net>,
Claudiu Manoil <claudiu.manoil@nxp.com>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 4/4] powerpc: remove orphaned MPC85xx kernel config fragments.
Date: Tue, 21 Feb 2023 22:49:30 +0100 [thread overview]
Message-ID: <20230221214930.35ttgzntv2vfwlo6@pali> (raw)
In-Reply-To: <Y/U3vIKzkKJAc5iU@windriver.com>
On Tuesday 21 February 2023 16:29:32 Paul Gortmaker wrote:
> [Re: [PATCH 4/4] powerpc: remove orphaned MPC85xx kernel config fragments.] On 21/02/2023 (Tue 21:03) Pali Roh??r wrote:
>
> > On Tuesday 21 February 2023 14:46:37 Paul Gortmaker wrote:
> > > None of these have a reference anymore anywhere, such as like this:
> > >
> > > arch/powerpc/Makefile: $(call merge_into_defconfig,mpc85xx_base.config,\
> > >
> > > As such, we probably should just clean up and remove them.
> > >
> > > Cc: Scott Wood <oss@buserror.net>
> > > Cc: Michael Ellerman <mpe@ellerman.id.au>
> > > Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> > > Cc: Paul Mackerras <paulus@samba.org>
> > > Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> > > ---
> > > arch/powerpc/configs/85xx-32bit.config | 5 -
> > > arch/powerpc/configs/85xx-hw.config | 139 -------------------------
> > > arch/powerpc/configs/85xx-smp.config | 2 -
> > > 3 files changed, 146 deletions(-)
> > > delete mode 100644 arch/powerpc/configs/85xx-32bit.config
> > > delete mode 100644 arch/powerpc/configs/85xx-hw.config
> > > delete mode 100644 arch/powerpc/configs/85xx-smp.config
> >
> > This change is likely going to break mpc85xx platform because defconfig
> > files includes all these files which you are going to remove. For
> > example in arch/powerpc/Makefile is:
> >
> > PHONY += mpc85xx_smp_defconfig
> > mpc85xx_smp_defconfig:
> > $(call merge_into_defconfig,mpc85xx_base.config,\
> > 85xx-32bit 85xx-smp 85xx-hw fsl-emb-nonhw)
>
> OK, it seems you've answered a question for me. That being "why didn't
> grep find a reference to these fragments?"
>
> It seems the ".config" extension is optional?
I really do not know. (And I'm not sure if I want to know answer :D)
> This seems inconsistent at best, to reference some files with the
> .config extension and others without it. Not blaming you for that,
> but it is probably something that needs looking into.
I agree it is inconsistent. But it was there before I looked or touched
any powerpc code. So it looks like something which nobody wanted to
cleanup because "it works" and had no motivation.
> I am fine with dropping this config frag patch as we figure that out.
>
> Paul.
> --
>
> >
> > And for P2020 boards I'm using mpc85xx_smp_defconfig configuration as
> > this one compiles SMP kernel, ideal for P2020 which is dual-core SoC.
next prev parent reply other threads:[~2023-02-21 21:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 19:46 [RFC PATCH 0/4] Remove some e500/MPC85xx evaluation platforms Paul Gortmaker
2023-02-21 19:46 ` [PATCH 1/4] powerpc: drop MPC8540_ADS and MPC8560_ADS platform support Paul Gortmaker
2023-02-21 19:46 ` [PATCH 2/4] powerpc: drop MPC85xx_CDS " Paul Gortmaker
2023-02-21 19:46 ` [PATCH 3/4] powerpc: drop MPC8568_MDS / P1021_MDS " Paul Gortmaker
2023-02-21 19:46 ` [PATCH 4/4] powerpc: remove orphaned MPC85xx kernel config fragments Paul Gortmaker
2023-02-21 20:03 ` Pali Rohár
2023-02-21 21:29 ` Paul Gortmaker
2023-02-21 21:49 ` Pali Rohár [this message]
2023-03-02 23:30 ` Crystal Wood
2023-03-03 0:25 ` Paul Gortmaker
2023-02-21 20:13 ` [RFC PATCH 0/4] Remove some e500/MPC85xx evaluation platforms Pali Rohár
2023-02-21 21:35 ` Paul Gortmaker
2023-02-21 22:00 ` Pali Rohár
2023-02-27 21:16 ` Li Yang
2023-04-14 2:13 ` Michael Ellerman
2023-04-14 23:29 ` Leo Li
2023-04-17 15:00 ` Paul Gortmaker
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=20230221214930.35ttgzntv2vfwlo6@pali \
--to=pali@kernel.org \
--cc=claudiu.manoil@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oss@buserror.net \
--cc=paul.gortmaker@windriver.com \
--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).