From: Arnd Bergmann <arnd@arndb.de> To: Christophe Leroy <christophe.leroy@c-s.fr> Cc: Michael Ellerman <mpe@ellerman.id.au>, Benjamin Herrenschmidt <benh@kernel.crashing.org>, Paul Mackerras <paulus@samba.org>, Michal Simek <michal.simek@xilinx.com>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, linuxppc-dev <linuxppc-dev@lists.ozlabs.org> Subject: Re: [PATCH v2 09/11] powerpc/platforms: Move files from 4xx to 44x Date: Tue, 31 Mar 2020 20:38:35 +0200 [thread overview] Message-ID: <CAK8P3a1jM8W72iH0qmMLRBRsv8ANYdL0xro0iWty3FvM6HTd0A@mail.gmail.com> (raw) In-Reply-To: <74e76b4e-5e4f-f3de-96a8-f6a451b3243a@c-s.fr> On Tue, Mar 31, 2020 at 6:19 PM Christophe Leroy <christophe.leroy@c-s.fr> wrote: > Le 31/03/2020 à 18:04, Arnd Bergmann a écrit : > > That has the risk of breaking user's defconfig files, but given the > > small number of users, it may be nicer for consistency. In either > > case, the two symbols should probably hang around as synonyms, > > the question is just which one is user visible. > > > > Not sure it is a good idea to keep two synonyms. In the past we made our > best to remove synonyms (We had CONFIG_8xx and CONFIG_PPC_8xx being > synonyms, we had CONFIG_6xx and CONFIG_BOOK3S_32 and > CONFIG_PPC_STD_MMU_32 being synonyms). > I think it is a lot cleaner when we can avoid synonyms. Ok, fair enough. > By the way I already dropped CONFIG_4xx in previous patch (8/11). It was > not many 4xx changed to 44x. It would be a lot more in the other way > round I'm afraid. Right. Maybe stay with 44x for both then (as in your current patches), as it means changing less in a part of the code that has few users anyway. Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de> To: Christophe Leroy <christophe.leroy@c-s.fr> Cc: Michal Simek <michal.simek@xilinx.com>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, Paul Mackerras <paulus@samba.org>, linuxppc-dev <linuxppc-dev@lists.ozlabs.org> Subject: Re: [PATCH v2 09/11] powerpc/platforms: Move files from 4xx to 44x Date: Tue, 31 Mar 2020 20:38:35 +0200 [thread overview] Message-ID: <CAK8P3a1jM8W72iH0qmMLRBRsv8ANYdL0xro0iWty3FvM6HTd0A@mail.gmail.com> (raw) In-Reply-To: <74e76b4e-5e4f-f3de-96a8-f6a451b3243a@c-s.fr> On Tue, Mar 31, 2020 at 6:19 PM Christophe Leroy <christophe.leroy@c-s.fr> wrote: > Le 31/03/2020 à 18:04, Arnd Bergmann a écrit : > > That has the risk of breaking user's defconfig files, but given the > > small number of users, it may be nicer for consistency. In either > > case, the two symbols should probably hang around as synonyms, > > the question is just which one is user visible. > > > > Not sure it is a good idea to keep two synonyms. In the past we made our > best to remove synonyms (We had CONFIG_8xx and CONFIG_PPC_8xx being > synonyms, we had CONFIG_6xx and CONFIG_BOOK3S_32 and > CONFIG_PPC_STD_MMU_32 being synonyms). > I think it is a lot cleaner when we can avoid synonyms. Ok, fair enough. > By the way I already dropped CONFIG_4xx in previous patch (8/11). It was > not many 4xx changed to 44x. It would be a lot more in the other way > round I'm afraid. Right. Maybe stay with 44x for both then (as in your current patches), as it means changing less in a part of the code that has few users anyway. Arnd
next prev parent reply other threads:[~2020-03-31 18:38 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-31 7:49 [PATCH v2 01/11] powerpc: Mark 4xx as Orphan in MAINTAINERS Christophe Leroy 2020-03-31 7:49 ` Christophe Leroy 2020-03-31 7:49 ` [PATCH v2 02/11] powerpc: Remove Xilinx PPC405/PPC440 support Christophe Leroy 2020-03-31 7:49 ` Christophe Leroy 2020-03-31 7:49 ` [PATCH v2 03/11] powerpc/40x: Remove 40x platforms Christophe Leroy 2020-03-31 7:49 ` Christophe Leroy 2020-03-31 7:49 ` [PATCH v2 04/11] powerpc/boot: Remove all " Christophe Leroy 2020-03-31 7:49 ` Christophe Leroy 2020-03-31 7:49 ` [PATCH v2 05/11] powerpc: Remove support for 40x Christophe Leroy 2020-03-31 7:49 ` Christophe Leroy 2020-03-31 7:49 ` [PATCH v2 06/11] powerpc: Remove IBM405 Erratum #77 Christophe Leroy 2020-03-31 7:49 ` Christophe Leroy 2020-03-31 7:49 ` [PATCH v2 07/11] powerpc/xmon: Remove PPC403 and PPC405 Christophe Leroy 2020-03-31 7:49 ` Christophe Leroy 2020-03-31 15:10 ` Arnd Bergmann 2020-03-31 15:10 ` Arnd Bergmann 2020-04-01 2:16 ` Michael Ellerman 2020-04-01 2:16 ` Michael Ellerman 2020-03-31 7:49 ` [PATCH v2 08/11] powerpc/4xx: Remove CONFIG_4xx Christophe Leroy 2020-03-31 7:49 ` Christophe Leroy 2020-03-31 7:49 ` [PATCH v2 09/11] powerpc/platforms: Move files from 4xx to 44x Christophe Leroy 2020-03-31 7:49 ` Christophe Leroy 2020-03-31 15:14 ` Arnd Bergmann 2020-03-31 15:14 ` Arnd Bergmann 2020-03-31 15:26 ` Christophe Leroy 2020-03-31 15:26 ` Christophe Leroy 2020-03-31 16:04 ` Arnd Bergmann 2020-03-31 16:04 ` Arnd Bergmann 2020-03-31 16:19 ` Christophe Leroy 2020-03-31 16:19 ` Christophe Leroy 2020-03-31 18:38 ` Arnd Bergmann [this message] 2020-03-31 18:38 ` Arnd Bergmann 2020-04-01 2:20 ` Michael Ellerman 2020-04-01 2:20 ` Michael Ellerman 2020-03-31 7:49 ` [PATCH v2 10/11] powerpc/pgtable: Drop PTE_ATOMIC_UPDATES Christophe Leroy 2020-03-31 7:49 ` Christophe Leroy 2020-03-31 7:49 ` [PATCH v2 11/11] powerpc/32: Replace RFI by rfi Christophe Leroy 2020-03-31 7:49 ` Christophe Leroy
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=CAK8P3a1jM8W72iH0qmMLRBRsv8ANYdL0xro0iWty3FvM6HTd0A@mail.gmail.com \ --to=arnd@arndb.de \ --cc=benh@kernel.crashing.org \ --cc=christophe.leroy@c-s.fr \ --cc=linux-kernel@vger.kernel.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=michal.simek@xilinx.com \ --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: linkBe 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.