From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Crystal Wood <oss@buserror.net>
Cc: Pali Roh?r <pali@kernel.org>, Li Yang <leoyang.li@nxp.com>,
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: Thu, 2 Mar 2023 19:25:04 -0500 [thread overview]
Message-ID: <ZAE+YBeCB8ql/qrj@windriver.com> (raw)
In-Reply-To: <8f1b02433cbeb90fab982a0b5377e8558e4eb5d3.camel@buserror.net>
[Re: [PATCH 4/4] powerpc: remove orphaned MPC85xx kernel config fragments.] On 02/03/2023 (Thu 17:30) Crystal Wood wrote:
> On Tue, 2023-02-21 at 22:49 +0100, Pali Roh??r wrote:
> > 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)
>
> It's not optional; you have to leave it off:
>
> # Used to create 'merged defconfigs'
> # To use it $(call) it with the first argument as the base defconfig
> # and the second argument as a space separated list of .config files to merge,
> # without the .config suffix.
> define merge_into_defconfig
> ...
>
> > > 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.
>
> No, it's intentional to reduce verbosity. If by "inconsistent" you're
> referring to mpc85xx_base.config, that argument sometimes refers to _defconfig
> files (i.e. the pseries targets which were the initial user of
> merge_into_config) so that argument can't autoappend .config.
Thanks for the detailed explanation. As I believe I said elsewhere, I
wouldn't be submitting this change once I understood the use case. Plus
it wasn't significant in reducing our overall maintain/build/boot kernel
overhead in v6.4+ in linux-next etc. --- as that was the real goal here.
I deleted our various BSPs years ago because I didn't think it was fair
or reasonable to expect other people to update/carry them on our behalf.
I would hope that is a statement that everyone could get behind.
Thanks,
Paul.
--
>
> -Crystal
>
next prev parent reply other threads:[~2023-03-03 0:26 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
2023-03-02 23:30 ` Crystal Wood
2023-03-03 0:25 ` Paul Gortmaker [this message]
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=ZAE+YBeCB8ql/qrj@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=claudiu.manoil@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oss@buserror.net \
--cc=pali@kernel.org \
--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 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.