linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Martin Kennedy <hurricos@gmail.com>
To: "Pali Rohár" <pali@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>, Leo Li <leoyang.li@nxp.com>,
	Crystal Wood <oss@buserror.net>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	Claudiu Manoil <claudiu.manoil@nxp.com>,
	Paul Mackerras <paulus@samba.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [RFC PATCH 0/4] Remove some e300/MPC83xx evaluation platforms
Date: Sat, 4 Mar 2023 13:35:08 -0500	[thread overview]
Message-ID: <CANA18UwqhKpfCEdxFcwc6k3jCgW7cf=0_g9cQCt1pVOCZVBJpQ@mail.gmail.com> (raw)
In-Reply-To: <20230304093710.tjdqbvdfqg7bgnyv@pali>

On Sat, Mar 4, 2023 at 4:37 AM Pali Rohár <pali@kernel.org> wrote:
>
> On Saturday 04 March 2023 07:31:49 Christophe Leroy wrote:
> > Le 03/03/2023 à 20:41, Crystal Wood a écrit :
> > > On Fri, 2023-03-03 at 10:14 +0100, Arnd Bergmann wrote:
> > >> 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:
> > >>
> > >> $ git log --no-merges --format="%an" v5.0.. arch/powerpc/platforms/[458e]* |
> > >> sort | uniq -c | sort -rn | grep -vw 1
> > >>       61 Christophe Leroy
> > >>       12 Michael Ellerman
> > >>       11 Thomas Gleixner
> > >>       11 Oliver O'Halloran
> > >>       11 Liang He
> > >>        7 Uwe Kleine-König
> > >>        6 Nick Child
> > >>        4 Rasmus Villemoes
> > >>        4 Randy Dunlap
> > >>        4 Mike Rapoport
> > >>        4 Julia Lawall
> > >>        4 Andy Shevchenko
> > >>        3 Xiaoming Ni
> > >>        3 Nicholas Piggin
> > >>        3 Marc Zyngier
> > >>        3 Christophe JAILLET
> > >>        3 Christoph Hellwig
> > >>        2 Paul Gortmaker
> > >>        2 Mathieu Malaterre
> > >>        2 Markus Elfring
> > >>        2 Jordan Niethe
> > >>        2 Dmitry Torokhov
> > >>        2 Arnd Bergmann
> > >>
> > >> Pretty much everyone else on the list above only did treewide
> > >> cleanups, dead code removal or compile-time fixes, while Christophe
> > >> is the one that fixed machine specific bugs and added new features.
> > >
> > > Speaking of that, I'd be fine with Christophe replacing me in the "LINUX FOR
> > > POWERPC EMBEDDED PPC83XX AND PPC85XX" entry, given that he's been way more
> > > involved than me lately.
> >
> > MPC83XX yes I can, I have MPC8321E Hardware, but PPC85XX I'm not sure. I
> > don't know much more than what I can experiment with QEMU.
> >
> > Maybe Pali for MPC85XX ?
> >
> > Christophe
>
> I have P2020 SMP HW (mpc85xx platform) which I use on daily usage. So yes, I can help.
>
> Martin Kennedy has other P1/P2 mpc85xx hardware and is working on Linux
> support for it. So maybe can be interested in this discussion. I'm CCing.

I have mpc85xx hardware, mostly access points adapted from the
P1020WLAN board, but I am frankly a hobbyist. I do my work under
OpenWrt, and I have no relationship with the manufacturers of these
devices.

I only catch regressions on my boards when changes are backported to
the LTS kernel OpenWrt uses (so, presently, 5.15).

Martin

  reply	other threads:[~2023-03-04 18:36 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 [this message]
2023-03-09 10:41                 ` Michael Ellerman
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='CANA18UwqhKpfCEdxFcwc6k3jCgW7cf=0_g9cQCt1pVOCZVBJpQ@mail.gmail.com' \
    --to=hurricos@gmail.com \
    --cc=arnd@arndb.de \
    --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=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).