All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Rob Herring <robh+dt@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Arnd Bergmann <arnd@arndb.de>,
	Michael Ellerman <mpe@ellerman.id.au>,
	PowerPC <linuxppc-dev@lists.ozlabs.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Anatolij Gustschin <agust@denx.de>
Subject: Re: linux-next: build warnings in Linus' tree
Date: Tue, 12 Oct 2021 16:39:56 +0200	[thread overview]
Message-ID: <CAK8P3a1EcNuxT-w-8w-HDr2+idsP=vFZ3Cn27fX7o56GOuu_Cg@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqJE_GHnehBz-71BOGXfjm6q2p0u6FQA5KwO8zK_i1LpMQ@mail.gmail.com>

On Mon, Oct 11, 2021 at 10:42 PM Rob Herring <robh+dt@kernel.org> wrote:
> On Sun, Oct 10, 2021 at 4:27 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> FYI, u-boot removed mpc5xxx support in 2017, so maybe there's
> similarly not a need to keep them in the kernel? It does appear NXP
> will still sell you the parts though the last BSP was 2009.

Specifically, MPC5200B has a 15 year lifetime, which ends in
11 months from now. The original bplan/Genesi Efika 5K2 was
quite popular at the time it came out, and there are probably
still some of those hanging around, but they came with Open
Firmware rather than relying on the dts files that ship with the
kernel.

Grant Likely was the original maintainer for MPC52xx until 2011,
Anatolij Gustschin is still listed as maintainer since then but hasn't
been active in it for a while either. Anatolij can probably best judge
which of these boards are still in going to be used with future kernels,
but I suspect once you start removing bits from 52xx, the newer
but less common 512x platform can go away as well.

         Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Rob Herring <robh+dt@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Arnd Bergmann <arnd@arndb.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Anatolij Gustschin <agust@denx.de>,
	PowerPC <linuxppc-dev@lists.ozlabs.org>
Subject: Re: linux-next: build warnings in Linus' tree
Date: Tue, 12 Oct 2021 16:39:56 +0200	[thread overview]
Message-ID: <CAK8P3a1EcNuxT-w-8w-HDr2+idsP=vFZ3Cn27fX7o56GOuu_Cg@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqJE_GHnehBz-71BOGXfjm6q2p0u6FQA5KwO8zK_i1LpMQ@mail.gmail.com>

On Mon, Oct 11, 2021 at 10:42 PM Rob Herring <robh+dt@kernel.org> wrote:
> On Sun, Oct 10, 2021 at 4:27 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> FYI, u-boot removed mpc5xxx support in 2017, so maybe there's
> similarly not a need to keep them in the kernel? It does appear NXP
> will still sell you the parts though the last BSP was 2009.

Specifically, MPC5200B has a 15 year lifetime, which ends in
11 months from now. The original bplan/Genesi Efika 5K2 was
quite popular at the time it came out, and there are probably
still some of those hanging around, but they came with Open
Firmware rather than relying on the dts files that ship with the
kernel.

Grant Likely was the original maintainer for MPC52xx until 2011,
Anatolij Gustschin is still listed as maintainer since then but hasn't
been active in it for a while either. Anatolij can probably best judge
which of these boards are still in going to be used with future kernels,
but I suspect once you start removing bits from 52xx, the newer
but less common 512x platform can go away as well.

         Arnd

  reply	other threads:[~2021-10-12 14:40 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08  5:47 linux-next: build warnings in Linus' tree Stephen Rothwell
2021-10-08  5:47 ` Stephen Rothwell
2021-10-10 21:27 ` Stephen Rothwell
2021-10-10 21:27   ` Stephen Rothwell
2021-10-11 20:42   ` Rob Herring
2021-10-11 20:42     ` Rob Herring
2021-10-12 14:39     ` Arnd Bergmann [this message]
2021-10-12 14:39       ` Arnd Bergmann
2021-10-13 22:12       ` Anatolij Gustschin
2021-10-13 22:12         ` Anatolij Gustschin
2021-10-13 22:17         ` Rob Herring
2021-10-13 22:17           ` Rob Herring
2021-10-13 22:28           ` Anatolij Gustschin
2021-10-13 22:28             ` Anatolij Gustschin
2021-10-13 23:22             ` Rob Herring
2021-10-13 23:22               ` Rob Herring
2021-10-14  8:44         ` Arnd Bergmann
2021-10-14  8:44           ` Arnd Bergmann
2021-10-14 12:24           ` Anatolij Gustschin
2021-10-14 12:24             ` Anatolij Gustschin
  -- strict thread matches above, loose matches on Subject: below --
2022-06-14  6:57 Stephen Rothwell
2022-05-26  7:21 Stephen Rothwell
2022-01-27  4:30 Stephen Rothwell
2022-01-27  6:01 ` Christoph Hellwig
2022-01-27 16:44   ` Stephen Rothwell
2022-01-27  4:24 Stephen Rothwell
2021-11-22 22:44 Stephen Rothwell
2021-11-23  7:04 ` Borislav Petkov
2021-11-05  5:03 Stephen Rothwell
2021-10-12 10:56 Stephen Rothwell
2021-10-12 20:13 ` Randy Dunlap
2020-09-07 23:11 Stephen Rothwell
2020-09-08 13:14 ` Josh Poimboeuf
2020-09-09  0:15   ` Stephen Rothwell
2020-04-03 22:19 Stephen Rothwell
2020-04-03 23:16 ` Rob Herring
2020-04-03 23:31   ` Nicolas Saenz Julienne
2017-11-13 21:52 Stephen Rothwell
2017-11-13 22:03 ` Linus Torvalds
2013-07-04  4:58 Stephen Rothwell
2013-07-09 21:48 ` Nikolova, Tatyana E
2011-08-15  1:57 Stephen Rothwell
2011-05-23  1:25 Stephen Rothwell
2011-05-23  2:31 ` Eduardo Silva
2011-01-14  0:17 Stephen Rothwell
2011-01-14  0:09 Stephen Rothwell
2011-01-14  0:17 ` Andrew Morton
2011-01-14  1:06   ` Greg KH
2010-08-17  1:24 Stephen Rothwell
2010-08-30  1:42 ` Stephen Rothwell
2010-08-30  6:08   ` Zhang Rui
2010-09-03  2:01     ` Stephen Rothwell
2010-09-03  2:36     ` Len Brown
2010-09-17  4:26     ` Stephen Rothwell
2010-09-27 13:31       ` Stephen Rothwell
2010-08-07  2:21 Stephen Rothwell
2010-08-07  8:13 ` Vikas Chaudhary

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='CAK8P3a1EcNuxT-w-8w-HDr2+idsP=vFZ3Cn27fX7o56GOuu_Cg@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=agust@denx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=robh+dt@kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.