From: Michael Ellerman <mpe@ellerman•id.au>
To: Arnd Bergmann <arnd@arndb•de>,
Paul Gortmaker <paul.gortmaker@windriver•com>,
Christophe Leroy <christophe.leroy@csgroup•eu>
Cc: Scott Wood <oss@buserror•net>, Paul Mackerras <paulus@samba•org>,
Claudiu Manoil <claudiu.manoil@nxp•com>,
"linuxppc-dev@lists•ozlabs.org" <linuxppc-dev@lists•ozlabs.org>,
Leo Li <leoyang.li@nxp•com>
Subject: Re: [RFC PATCH 0/4] Remove some e300/MPC83xx evaluation platforms
Date: Thu, 09 Mar 2023 21:41:01 +1100 [thread overview]
Message-ID: <87edpy1a2q.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <3efa1e29-3be9-4047-beef-eb02762ae8db@app.fastmail.com>
"Arnd Bergmann" <arnd@arndb•de> writes:
> On Fri, Mar 3, 2023, at 02:04, Paul Gortmaker wrote:
>> 01/03/2023 (Wed 14:23) Christophe Leroy wrote:
>>> Le 28/02/2023 ?? 18:51, Arnd Bergmann a ??crit??:
>>> Hope it clarifies how those reference boards are used.
>>
>> It was really useful input and gave an insight into how things get used.
>>
>> But let me put a slightly different slant on things. If there is no
>> maintainer for the platform/architecture/CPU, then where is the
>> obligation for mainline to keep it up to date just for your company to
>> use the code/BSP as a reference?
>>
>> Do they continue to do this for one more year, or three or ... ???
>> Does someone list themselves in MAINTAINERS for arch/powerpc/83xx ?
> ...
>>
>> If you see change 0123abcdef breaks boot on your platform, you have a
>> legit voice to gripe about it right then and there. Don't wait!!!
>
> I think the answer here is that Christophe is already the only person
> that does this, so he is the de-facto maintainer for ppc32 regardless
> of whether he wants himself listed in the file or not:
Yes he is the de-facto 32-bit maintainer :)
He's listed as a reviewer on the converged 64-bit/32-bit maintainers
entry which is meant to reflect that:
LINUX FOR POWERPC (32-BIT AND 64-BIT)
M: Michael Ellerman <mpe@ellerman•id.au>
R: Nicholas Piggin <npiggin@gmail•com>
R: Christophe Leroy <christophe.leroy@csgroup•eu>
L: linuxppc-dev@lists•ozlabs.org
But we could add a separate 32-bit entry if people think that would make
things clearer.
Although I don't think we could run separate trees for 64-bit and
32-bit, there'd be too many conflicts, so in that way I think one entry
makes sense.
cheers
next prev parent reply other threads:[~2023-03-09 10:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 11:59 [RFC PATCH 0/4] Remove some e300/MPC83xx evaluation platforms Paul Gortmaker
2023-02-20 11:59 ` [PATCH 1/4] powerpc: drop MPC834x_MDS platform support Paul Gortmaker
2023-02-20 11:59 ` [PATCH 2/4] powerpc: drop MPC836x_MDS " Paul Gortmaker
2023-02-20 11:59 ` [PATCH 3/4] powerpc: drop MPC837x_MDS " Paul Gortmaker
2023-02-20 11:59 ` [PATCH 4/4] powerpc: drop MPC832x_MDS " Paul Gortmaker
2023-02-20 22:40 ` [RFC PATCH 0/4] Remove some e300/MPC83xx evaluation platforms Leo Li
2023-02-24 21:16 ` Leo Li
2023-02-25 16:50 ` Paul Gortmaker
2023-02-25 22:49 ` Arnd Bergmann
2023-02-27 20:42 ` Li Yang
2023-02-27 20:48 ` Li Yang
2023-02-28 10:03 ` Joakim Tjernlund
2023-02-28 17:51 ` Arnd Bergmann
2023-02-28 18:20 ` Li Yang
2023-03-01 14:23 ` Christophe Leroy
2023-03-01 14:45 ` Arnd Bergmann
2023-03-03 1:04 ` Paul Gortmaker
2023-03-03 9:14 ` Arnd Bergmann
2023-03-03 19:41 ` Crystal Wood
2023-03-04 7:31 ` Christophe Leroy
2023-03-04 9:37 ` Pali Rohár
2023-03-04 18:35 ` Martin Kennedy
2023-03-09 10:41 ` Michael Ellerman [this message]
2023-02-25 7:40 ` Christophe Leroy
2023-02-25 16:20 ` Paul Gortmaker
2023-04-26 12:10 ` Michael Ellerman
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=87edpy1a2q.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=arnd@arndb$(echo .)de \
--cc=christophe.leroy@csgroup$(echo .)eu \
--cc=claudiu.manoil@nxp$(echo .)com \
--cc=leoyang.li@nxp$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=oss@buserror$(echo .)net \
--cc=paul.gortmaker@windriver$(echo .)com \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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